The system-wide /tmp is not accessible by strictly-confined snaps, so
/tmp/chromium-home won't work either.
In any case this looks like a limitation hard-coded in snapd, which
won't create $SNAP_USER_DATA if $HOME is not in /home. So this is not
specific to the chromium snap. I'll add a snapd task to the bug.
As a workaround (I realize this is less than ideal), could you maybe
create a user with a home directory in /home just for this purpose, and
have have your server process run chromium as this user?
** Summary changed:
- [snap] Cannot run headless chromium as user www-data
+ [snap] Cannot run chromium as user www-data because home directory is /var/www
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849371
Title:
[snap] Cannot run chromium as user www-data because home directory is
/var/www
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849371/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
