[Bug 1659719] Re: ssh can't call a binary from a snap without the full path
Michael Hudson-Doyle
1659719 at bugs.launchpad.net
Thu Aug 20 23:05:12 UTC 2020
The focal autopkgtest failures are in cyrus-imapd:
Mail::JMAPTalk version 0.15 required--this is only version 0.13 at ./Cassandane/Cyrus/JMAPCore.pm line 47.
BEGIN failed--compilation aborted at ./Cassandane/Cyrus/JMAPCore.pm line 47.
This seems very unlikely to be due to pam, and it happens with the
version of pam anyway. The other failure is kopanocore/armhf which is
known flaky:
https://autopkgtest.ubuntu.com/packages/k/kopanocore/focal/armhf (I've
retried it anyway).
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
Status in Snappy:
Fix Committed
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in openssh package in Ubuntu:
Confirmed
Status in pam package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
New
Status in openssh source package in Xenial:
New
Status in pam source package in Xenial:
New
Status in livecd-rootfs source package in Bionic:
New
Status in openssh source package in Bionic:
New
Status in pam source package in Bionic:
Fix Committed
Status in livecd-rootfs source package in Focal:
New
Status in openssh source package in Focal:
New
Status in pam source package in Focal:
Fix Committed
Status in livecd-rootfs source package in Groovy:
Fix Released
Status in openssh source package in Groovy:
Confirmed
Status in pam source package in Groovy:
Fix Released
Status in openssh package in Debian:
New
Bug description:
[impact]
ssh can't call a binary from a snap, it will only work using the full path.
[test case]
Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh <container-ip> go version" and check the binary is found.
[regression potential]
It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy.
[original description]
Let's say I have the hello snap installed in 192.168.122.24. Then:
elopio at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
elopio at 192.168.122.24's password:
bash: hello: command not found
elopio at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
elopio at 192.168.122.24's password:
Hello, world!
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions
More information about the foundations-bugs
mailing list