6 replies

Problem with gog keyring in Docker

✅Solved

Goal: Automate

gog

gog

commands (Gmail/Calendar read/write) from the agent without manual passphrase entry.

Current Problem:
We have successfully authenticated

gog

gog

for my email using

gog auth credentials ...

gog auth credentials ...

and

gog auth add ... --manual

gog auth add ... --manual

. The tokens are stored in the

gog-config

gog-config

volume. However, when the agent tries to run any

gog

gog

command (e.g.,

gog gmail search ...

gog gmail search ...

), it consistently prompts for:

Enter passphrase to unlock "/home/node/.config/gogcli/keyring":

Enter passphrase to unlock "/home/node/.config/gogcli/keyring":

...and fails with

no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD

no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD

.

Attempts to fix
no TTY
no TTY
/
keyring
keyring
prompt:
1. Set
GOG_KEYRING_PASSWORD
GOG_KEYRING_PASSWORD
as an environment variable in
.env
.env
and
docker-compose.override.yml
docker-compose.override.yml
: This does not work.

gog

gog

still prompts interactively, ignoring the env var.
2. gog auth login --no-input
gog auth login --no-input
(and other combinations): The

--no-input

--no-input

flag for

login

login

does not prevent the keyring passphrase prompt.

Observations:
- The passphrase is known.
- The issue is

gog

gog

's interactive prompt for the keyring passphrase in a headless Docker environment.

Question for Experts:
1. What is the definitive, robust method to provide the
gog
gog
keyring passphrase to
gogcli
gogcli
in a non-interactive Docker environment (e.g., via environment variable, a flag, or a
setupCommand
setupCommand
that actually works)?
2. Is there a way to configure

gog

gog

to store its tokens unencrypted in the keyring (if that's a security-acceptable option for a personal setup), or to prevent it from asking for a passphrase at all?
3. If

GOG_KEYRING_PASSWORD

GOG_KEYRING_PASSWORD

should work, what are the precise steps to ensure it's correctly picked up by

gogcli

gogcli

in a

docker run

docker run

context?

Solution

Based on the gogcli documentation, here's what's needed:

The Definitive Solution

1. Set BOTH environment variables:

export GOG_KEYRING_BACKEND=file
export GOG_KEYRING_PASSWORD='your-passphrase-here'

export GOG_KEYRING_BACKEND=file
export GOG_KEYRING_PASSWORD='your-passphrase-here'

The

GOG_KEYRING_BACKEND=file

GOG_KEYRING_BACKEND=file

is critical — it forces the encrypted file backend and tells gog to expect a password from the environment.

2. Docker container setup:

Make sure these are passed to the container, not just in the host's

.env

.env

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

6 replies

Eddy

Problem with gog keyring in Docker

✅Solved

Goal: Automate

gog

gog

commands (Gmail/Calendar read/write) from the agent without manual passphrase entry.

Current Problem:
We have successfully authenticated

gog

gog

for my email using

gog auth credentials ...

gog auth credentials ...

and

gog auth add ... --manual

gog auth add ... --manual

. The tokens are stored in the

gog-config

gog-config

volume. However, when the agent tries to run any

gog

gog

command (e.g.,

gog gmail search ...

gog gmail search ...

), it consistently prompts for:

Enter passphrase to unlock "/home/node/.config/gogcli/keyring":

Enter passphrase to unlock "/home/node/.config/gogcli/keyring":

...and fails with

no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD

no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD

gog

gog

still prompts interactively, ignoring the env var.
2. gog auth login --no-input
gog auth login --no-input
(and other combinations): The

--no-input

--no-input

flag for

login

login

does not prevent the keyring passphrase prompt.

Observations:
- The passphrase is known.
- The issue is

gog

gog

gog

gog

to store its tokens unencrypted in the keyring (if that's a security-acceptable option for a personal setup), or to prevent it from asking for a passphrase at all?
3. If

GOG_KEYRING_PASSWORD

GOG_KEYRING_PASSWORD

should work, what are the precise steps to ensure it's correctly picked up by

gogcli

gogcli

in a

docker run

docker run

context?

Solution

Based on the gogcli documentation, here's what's needed:

The Definitive Solution

1. Set BOTH environment variables:

export GOG_KEYRING_BACKEND=file
export GOG_KEYRING_PASSWORD='your-passphrase-here'

export GOG_KEYRING_BACKEND=file
export GOG_KEYRING_PASSWORD='your-passphrase-here'

The

GOG_KEYRING_BACKEND=file

GOG_KEYRING_BACKEND=file

.env

.env

Jump to solution

Problem with gog keyring in Docker

The Definitive Solution

Problem with gog keyring in Docker

The Definitive Solution

Similar Threads

Similar Threads

Similar Threads