snap can not run /usr/bin/ssh => docker cannot use remote context #169
Assignees
Labels
bug
Something isn't working
Comments
hartmutobendorf
added a commit
to hartmutobendorf/docker-snap
that referenced
this issue
Aug 21, 2024
canonical#170 added ssh-keys interface added ssh-public-keys interface added openssh-client for staging added bind-file layout for /use/bin/ssh
hartmutobendorf
added a commit
to hartmutobendorf/docker-snap
that referenced
this issue
Aug 21, 2024
canonical#170 added ssh-keys interface added ssh-public-keys interface added openssh-client for staging added bind-file layout for /use/bin/ssh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
snap execution of /usr/bin/ssh fails => remote context can not be used
Why this is important
When running docker in a VM, or on a production host, I cannot manage the containers from my local machine.
This also means I cannot use/access containers in my IDE (VS Code). Running a docker blueprint in multipass or lxd is only possible with an install of the upstream, unsnapped docker.
To reproduce:
docker context create rem --docker "host=ssh://user@host" docker context use rem docker psfails with the error message
error during connect: Get "http://docker.example.com/v1.24/containers/json": fork/exec /usr/bin/ssh: permission deniedThe text was updated successfully, but these errors were encountered: