You are not logged in.

#1 2018-03-15 09:51:26

renordw
Member
From: New Mexico
Registered: 2018-03-04
Posts: 56

Job for lxc-net.service failed?

I'm following along this guide to create a container, https://wiki.archlinux.org/index.php/Linux_Containers

but I'm failing at this point

systemctl start lxc-net 
● lxc-net.service - LXC network bridge setup
   Loaded: loaded (/usr/lib/systemd/system/lxc-net.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-03-15 03:43:18 MDT; 8s ago
  Process: 2849 ExecStart=/usr/lib/lxc/lxc-net start (code=exited, status=1/FAILURE)
 Main PID: 2849 (code=exited, status=1/FAILURE)
 

I am currently using the Linux kernel, which has user namespaces enabled. Any suggestions?

Offline

#2 2018-03-15 14:30:05

renordw
Member
From: New Mexico
Registered: 2018-03-04
Posts: 56

Re: Job for lxc-net.service failed?

It fails with no `journalctl -xe` output.

Another hint? Am I supposed to replace the line in `etc/lxc/default.conf` with my MAC address where it says hwaddr?

lxc.net.0.type = empty
lxc.idmap = u 0 100000 65536
lxc.idmap = g 0 100000 65536
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

Offline

#3 2018-03-17 01:50:58

renordw
Member
From: New Mexico
Registered: 2018-03-04
Posts: 56

Re: Job for lxc-net.service failed?

Well. Something crazy happened. After tinkering with these files, and trying to create a bridge, many of the drivers became uninstalled during a routine pacman -Su. The one that was particularly annoying was the WiFi driver wlp9so was erased, and the system was looking for enp9s0 instead.

On boot I would randomly get either the error: "A job is running for subsys-wlp9s0" each boot, or "A job is running for enp9s0", and I could not modprobe either of them. Also, my mouse and keyboard drivers got automagically uninstalled. I could not log into the system to uninstall anything, so I tried the "pacstrap -C" to force reinstall the base files.

At that point the OS was invisible to grub, so instead of continuing down that path, I just reinstalled the whole OS.

Anyhow, if anybody has any experience with something similar, I would love to hear it so I can avoid this mistake next time.

Last edited by renordw (2018-03-17 02:30:54)

Offline

Board footer

Powered by FluxBB