New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

systemd-resolved|networkd|hostnamed fail to start in lxd container with v240+ #11588

Closed

xnox opened this issue Jan 29, 2019 · 1 comment

Member

xnox commented Jan 29, 2019

This is similar to #10032
But this time around with apparmor, under lxd, on ubuntu
Regression from 1beab8b
Will be tracing this further now.

The text was updated successfully, but these errors were encountered:

Member Author

xnox commented Jan 29, 2019

$ lxc config set improved-kodiak raw.apparmor 'mount options=(ro,nodev,remount,bind),
mount options=(ro,nosuid,nodev,remount,bind),
mount options=(ro,nosuid,noexec,remount,strictatime),
mount options=(ro,nosuid,nodev,noexec,remount,bind),'

fixes things. Will run this past apparmor/lxd people to allow.

xnox closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment