Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39019 - [lxc] Missing directory, preventing simple lxc setup to work
Attached to Project:
Community Packages
Opened by Baptiste (zorun) - Monday, 24 February 2014, 00:16 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 February 2014, 08:43 GMT
Opened by Baptiste (zorun) - Monday, 24 February 2014, 00:16 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 February 2014, 08:43 GMT
|
DetailsSince lxc 1:1.0.0-1, some of my simpler LXC setups don't work anymore. They worked just fine with 1:0.9.0-5.
When using this simple network-only lxc config [1] and lauching the container with `lxc-start -n bridge-babel4 ./something.sh`, it outputs [2] and refuses to start. I'm not sure if this is an upstream issue or Archlinux-specific, but simply creating `/usr/lib/lxc/rootfs/dev` solves the issue. Thanks! [1] http://paste.aliens-lyon.fr/hrz [2] http://paste.aliens-lyon.fr/XAD |
This task depends upon