Thanks for the report, this exploratory work requires a lot more
attention from me.
It turns out that squid is offending snap confinement is many different
fronts (logging and working dir, on top of the setgid) and I need to
investigate what would be the best solution from the squid perspective.
For now, to unblock users and potential contributors, I've republished
it as devmode on 16 edge channel (so it's clear that it's not ready for
production) with a custom squid.conf that allows it to start (barely):
{{{
$ sudo snap install squid3 --devmode --channel=edge
14.99 MB / 14.99 MB
[========================================================>_] 100.00 % 3.07 MB/s
Name Version Rev Developer
squid3 3.5.16-3 5 cprov
$ sudo mkdir -m o+rw /var/snap/squid3/current/logs
$ squid3 -N
...
}}}
Current snapcraft setup and custom configuration can be found at
https://code.launchpad.net/~cprov/+git/squid-snap
Sorry for the inconvenience and misleading expectation I've caused.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585056
Title:
snapd not give privileges to squid3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1585056/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
