FS#61078 - [lxc] lxc@<containername>.service fails to load after upgrade to 3.1.0
Attached to Project:
Community Packages
Opened by Savyasachee Jha (savyajha) - Friday, 14 December 2018, 21:59 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 17 April 2020, 00:50 GMT
Opened by Savyasachee Jha (savyajha) - Friday, 14 December 2018, 21:59 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 17 April 2020, 00:50 GMT
|
Details
Description:
After the upgrade from 3.0.3 -> 3.1.0, it's not possible to start an Alpine Linux container using systemd as described in the wiki. The container exits almost immediately after starting and there's nothing in the logs. A downgrade fixes it immediately. There's no problem using lxc-start from the command line to start the container. Additional info: * package version(s): 1:3.0.3-1 Steps to reproduce: - Install lxc-1:3.0.3-1 from the repos - Follow steps in wiki to use unprivileged containers - Create unprivileged Alpine Linux container - Run said container using lxc@<name>.service (it runs) - Upgrade package to 1:3.1.0-1 - Try "systemctl start lxc@<name>.service" again - It exits after starting |
This task depends upon
The solution is to change our service unit to the attached.
[Service]
PIDFile=/run/lxc-%i.pid
ExecStart=
ExecStart=/usr/bin/lxc-start -d -p /run/lxc-%i.pid -n %i
That should tide us over while we wait for the change to be pushed.
BTW, you can run `systemctl edit lxc@` to get systemd to open your editor for you for overrides... see the wiki.
FS#63277is fixed, I'm having this issue.Any reason to not incorporate this fix, @spupykin / @sergej ?