Hi all,
I have setup a simple lxc/lxd containers to aarch64 platform to use with opennebula system. First I tested the lxc/lxd system to run properly but I have problem with it. After I launch debian10/aarch64 system, everything looks fine on the console output.
Creating debian10
Starting debian10
But when I execute /bin/bash. It replies like this.
error: Container is not running.
Here are the following outputs for debian10 container information and the log error.
root@pine1:/var/log/lxd/debian10# more lxc.conf
lxc.cap.drop = sys_time sys_module sys_rawio mac_admin mac_override
lxc.mount.auto = proc:rw sys:rw cgroup:mixed
lxc.autodev = 1
lxc.pts = 1024
lxc.mount.entry = /dev/fuse dev/fuse none bind,create=file,optional
lxc.mount.entry = /dev/net/tun dev/net/tun none bind,create=file,optional
lxc.mount.entry = /proc/sys/fs/binfmt_misc proc/sys/fs/binfmt_misc none rbind,create=dir,optional
lxc.mount.entry = /sys/fs/fuse/connections sys/fs/fuse/connections none rbind,create=dir,optional
lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none rbind,create=dir,optional
lxc.mount.entry = /sys/kernel/security sys/kernel/security none rbind,create=dir,optional
lxc.mount.entry = /dev/mqueue dev/mqueue none rbind,create=dir,optional
lxc.include = /usr/share/lxc/config/common.conf.d/
lxc.logfile = /var/log/lxd/debian10/lxc.log
lxc.loglevel = warn
lxc.arch = linux64
lxc.hook.pre-start = /usr/bin/lxd callhook /var/lib/lxd 5 start
lxc.hook.post-stop = /usr/bin/lxd callhook /var/lib/lxd 5 stop
lxc.tty = 0
lxc.utsname = debian10
lxc.mount.entry = /var/lib/lxd/devlxd dev/lxd none bind,create=dir 0 0
lxc.aa_profile = lxd-debian10_</var/lib/lxd>
lxc.seccomp = /var/lib/lxd/security/seccomp/debian10
lxc.id_map = u 0 100000 65536
lxc.id_map = g 0 100000 65536
lxc.environment = http_proxy=http://[fe80::1%eth0]:13128
lxc.rootfs = /var/lib/lxd/containers/debian10/rootfs
lxc.mount.entry = /var/lib/lxd/shmounts/debian10 dev/.lxd-mounts none bind,create=dir 0 0
root@pine1:/var/log/lxd/debian10# more lxc.log
lxc 20180401082858.881 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082858.881 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082900.943 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082900.943 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082901.468 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082901.468 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082901.468 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082901.696 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc 20180401082901.696 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
I am a totally newbie for lxc/lxd containers, could someone clarify the problem?
Thanks.
After installing debootstrap package, i overcome the problem. But now in ubuntu-container hostnamectl command cant executed, and after execution of hostnamectl command, systemd-hostnamed.service failed.
How can I debug what is going on with the hostnamectl command or affect the systemd.
Thanks.
Here is the ubuntu version of container.
ubuntu@c1-ubuntu:~$ more /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=“Ubuntu 16.04.4 LTS”
hostnamectl hanging has been a bit of a recurring problem, it’s systemd related and I think @brauner figured out the fix for it. If that’s the case, I’d expect it to eventually make its way into Ubuntu through a stable update.
Yeah, the service file sets PrivateDevices=yes which would fail but I recently sent a patch to systemd that got merged which should allow systemd-hostnamed to start.