/etc/environment does not include /snap/bin in $PATH
Bug #1660273 reported by
Nobuto Murata
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Low
|
Unassigned | ||
Snap Layer |
Fix Released
|
Critical
|
Unassigned | ||
cloud-images |
Invalid
|
Undecided
|
Unassigned | ||
snapd |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
/snap/bin is not in the system default path, and is only added to the path for interactive shells.
This means that snaps are not drop in replacements to Debian packages. All references to snapped executables not in interactive shells need to be updated to specify the full /snap/bin PATH, including but not limited to crontabs, systemd service definitions, Juju hook environments, and all applications running under one of these contexts.
A work around is to manually hack /etc/environment , but this is poor as the goal is to get snaps working out of the box.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
Changed in juju: | |
milestone: | 2.2.0 → none |
status: | Triaged → Invalid |
summary: |
- `juju run` does not include /snap/bin in $PATH + /etc/environment does not include /snap/bin in $PATH |
Changed in juju: | |
status: | New → Incomplete |
tags: | added: canonical-is |
To post a comment you must log in.
Juju does not alter the PATH of the host except to add the tools directory for unit hook executions.