-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Credentials Helper Fails after a few hours #1118
Comments
@mudged thanks for reporting the issue, we'll look into it. Just to confirm, there's no output if you run |
The process is no longer alive (only grep is shown) $ docker-credential-devpod list
Error retrieving list credentials: Post "http://localhost:12049/docker-credentials": dial tcp 127.0.0.1:12049: connect: connection refused $ ps -aux | grep credentials-server
mtx 111666 0.0 0.0 3324 1556 pts/0 S+ 15:13 0:00 grep credentials-server No lock file $ cat $TMPDIR/devpod-credentials.lock
cat: /devpod-credentials.lock: No such file or directory |
If I restart the DevContainer, I see the process but no lock file $ ps -aux | grep credentials-server
root 1040 0.0 0.1 1296652 51596 ? Sl 15:28 0:00 /usr/local/bin/devpod agent container credentials-server --user mtx --configure-git-helper --configure-docker-helper
mtx 13558 0.0 0.0 3324 1660 pts/0 S+ 15:30 0:00 grep credentials-server $ cat $TMPDIR/devpod-credentials.lock
cat: /devpod-credentials.lock: No such file or directory |
I have the same issue. After some time, the credentials server dies.
The credentials server is not running, but the lock file ( When the credentials server works it runs like this:
|
I experience exactly the same issue. Closing and re-opening VSCode help to restart the credentials server. |
Hey @mudged @AndriiTsok, this should be fixed with #1159 and released today or on monday |
What happened?
After a few hours of the DevContainer being up, calls to docker-credentials-devpod return
Error retrieving list credentials: Post "http://localhost:12049/docker-credentials": dial tcp 127.0.0.1:12049: connect: connection refused
This was initially working as expected. The same behaviour has been observed on different DevContainers and the same one (after restart)
What did you expect to happen instead?
Docker credential helper is still able to retrieve credentials
How can we reproduce the bug? (as minimally and precisely as possible)
Start DevContainer using DevPod (ssh provider, IntelliJ IDE, Windows 11 host, multipass Ubuntu VM).
Leave active for 1/2 hours and then run
docker-credentials-devpod list
.Local Environment:
DevPod Provider:
Anything else we need to know?
Inject docker credentials selected on provider
The text was updated successfully, but these errors were encountered: