Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
–> systemd-nspawn -bD ubuntu1404_test
Spawning container ubuntu1404_test on /frzclient/images/ubuntu1404_test.
Press ^] three times within 1s to kill container.
init: Unable to create device: /dev/kmsg
* Stopping Send an event to indicate plymouth is up [ OK ]
* Starting Clean /tmp directory [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Stopping Populate /dev filesystem [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Starting device node and kernel event manager [ OK ]
* Starting Signal sysvinit that local filesystems are mounted [ OK ]
* Starting configure network device security [ OK ]
* Starting Signal sysvinit that remote filesystems are mounted [ OK ]
* Starting load modules from /etc/modules [ OK ]
* Stopping Mount filesystems on boot [ OK ]
* Stopping load modules from /etc/modules [ OK ]
* Starting flush early job output to logs [ OK ]
* Stopping flush early job output to logs [ OK ]
* Starting System V initialisation compatibility [ OK ]
* Starting configure virtual network devices [ OK ]
* Stopping System V initialisation compatibility [ OK ]
* Starting System V runlevel compatibility [ OK ]
* Starting Bridge file events into upstart [ OK ]
* Stopping System V runlevel compatibility [ OK ]
@acooks

This comment has been minimized.

Copy link

acooks commented Feb 11, 2015

I found this gist while searching for a solution to booting Ubuntu 12.04 in a systemd-nspawn container on Fedora 21.

The output looks very similar, so I assume this gist was posted after you ran into problems as well. Could you please link to the discussion or point me to the solution?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.