[Bug 1659719] Re: ssh can't call a binary from a snap without the full path

[Johan Ehnberg]

This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple releases a pain since some hosts may run the snap,
others installed by dpkg.

Is there any update on the intended direction?

-- 
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 Committed
Status in openssh package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  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