This might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1656024
Title:
Units using
I had the same problem using the varnishncsa service:
systemd[30274]: varnishncsa.service: Failed at step NETWORK spawning
/usr/bin/varnishncsa: Permission denied
Overriding PrivateNetwork to be false seems to work as a workoround.
** Also affects: varnish (Ubuntu)
Importance: Undecided
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm not sure how to use the "systemctl edit" command.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1656024
Title:
Units using PrivateNetwork=yes don't work inside user
Stéphane, thanks for looking into this. Is there a way I can set that by
default for any new lxd containers I create, as a workaround?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
You should be able to use "systemctl edit" to set PrivateNetwork=no as a
temporary workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1656024
Title:
Units using
6 matches
Mail list logo
