config validate no longer works on snap version about circleci-cli HOT 5 CLOSED

Someone with the same issue: https://discuss.circleci.com/t/circleci-apparmor-issue-for-validation-on-ubuntu-linux/24411

from circleci-cli.

+1

from circleci-cli.

My hunch is that this is caused by our Snap confinement setting being strict.

https://docs.snapcraft.io/reference/confinement

Strict confinement gives you the following readable and/or writable paths:

• /snap/<snap>/ (read-only, snap install path)
• /var/snap/<snap>/ (read/write, per-revision data)
• /var/snap/<snap>/common (read/write, common data)
• /home/$USER/snap/<snap>/<revision> (read/write, per-revision user data)
• /home/$USER/snap/<snap>/common (read/write, common user data)

When running the binary through snap, we should be writing settings to /home/$USER/snap/<snap>/common I guess.

from circleci-cli.

If we detect SNAP_USER_COMMON at runtime, we should be able to use it as the home directory.

from circleci-cli.

I have a potential fix for this. Waiting for permissions on this repo so that I can open a PR.

from circleci-cli.