For a Snappy binary, $SNAP_APP_USER_DATA_PATH is created within the binary wrapper right before the binary is launched[1]. However, no such logic exists for services, where the $SNAP_APP_USER_DATA_PATH resolves to /root/apps/... . This means that if a Snappy service tries to use $SNAP_APP_USER_DATA_PATH, it's trying to use a directory that doesn't exist. This leads services to either fail or try to create /root/apps, which obviously can't happen.
For a Snappy binary, $SNAP_APP_ USER_DATA_ PATH is created within the binary wrapper right before the binary is launched[1]. However, no such logic exists for services, where the $SNAP_APP_ USER_DATA_ PATH resolves to /root/apps/... . This means that if a Snappy service tries to use $SNAP_APP_ USER_DATA_ PATH, it's trying to use a directory that doesn't exist. This leads services to either fail or try to create /root/apps, which obviously can't happen.
[1]: https:/ /github. com/ubuntu- core/snappy/ blob/master/ snappy/ click.go# L149