I already created a new Ubuntu Host and the container works fine. The question is: We have been living under the assumption that containers act like virtual machines, you may move them from host to host. It is not the case, I can see. A Fedora 20 container created under Ubuntu will never start under a Fedora 20 host. In my opinion this is a big flaw. Containers built by libvirt are truly portable, I have already verified that. I think we should fix this.
On Tue, Jun 17, 2014 at 9:23 AM, Serge Hallyn <[email protected]> wrote: > Quoting CDR ([email protected]): >> I copied an LXC container fro Ubuntu Server to Fedora 20 and when I >> start it I get >> xc-start -n masterfe >> systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX >> +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) >> Detected virtualization 'lxc'. >> >> Welcome to Fedora 20 (Heisenbug)! >> >> Set hostname to <masterfe>. >> No control group support available, not creating root group. >> [ OK ] Reached target Remote File Systems. >> Socket service systemd-journald.service not loaded, refusing. >> [FAILED] Failed to listen on Journal Socket. > > Two suggestions for investigating: > > 1. create a new fedora container on the ubuntu host, see if it > has the same behavior. > > 2. Look at the systemd source and see under what conditions the two > lines above occur. > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
