I’m using Kamal inside some VSCode hosted devcontainers. .devcontainer/devcontainer.json includes ghcr.io/devcontainers/features/docker-outside-of-docker:
After a lot of trouble getting passwords to work, I did get things running, and I was able to create other devcontainers and also use Kamal to deploy with them.But this morning they’ve all stopped working except for one. I get this error
INFO [7fdf34e4] Running docker login some-docker-registry -u [REDACTED] -p [REDACTED] as vscode@localhost
Finished all in 0.3 seconds
ERROR (SSHKit::Command::Failed): docker exit status: 256
docker stdout: Nothing written
docker stderr: WARNING! Using --password via the CLI is insecure. Use --password-stdin.
As far as I can see the devcontainer where kamal deploy works is the same as the ones where it doesn’t. So I’m completely mystified.
Configuring Kamal to run inside a devcontainer is not a simple process. So some documentation on this would be nice. I’ll write some once I’ve worked out a standard procedure but I’m still in the banging head on table stage.
For now I’ve given up trying to run Kamal from inside a docker container. It’ll trick you into thinking it works, and then one morning it just won’t work and you’ll spend hours trying to find out why and never find the answer.
So for now I’ve given up trying to run Kamal inside the dev container, I’m just running it on the host.
One minor change to my original post. All containers stopped being able run Kamal except 2, not except 1. I’ve not been able to find the difference between the ones that work and the ones that don’t.
The other thing is that when it runs OK you don’t see the warning about using --password instead of --password-stdin . I’ll guess that because the Kamal developers never got an error when logging in they never saw that warning.