[lxc-users] Serge Hallyn's article "Publishing LXD images"

[david.andel at bli.uzh.ch]

But now happens something strange:

When running 'lxc exec wily-with-upstart-1 /bin/bash' the prompt changes to root at wily-with-upstart-1 as expected, but then closes the shell in a few seconds, falling back on the host prompt.
This happens both in the original wily (with systemd) and in the wily-with-upstart containers, but not in a trusty container.
I haven't found any entries in /var/log in those containers during the time that this happens.

What could this be and how can I find the cause?

Thanks

-----"lxc-users" <lxc-users-bounces at lists.linuxcontainers.org> wrote: -----
To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
From: Serge Hallyn 
Sent by: "lxc-users" 
Date: 12/07/2015 16:21
Subject: Re: [lxc-users] Serge Hallyn's article "Publishing LXD images"

Quoting david.andel at bli.uzh.ch (david.andel at bli.uzh.ch):
> Hi all
> 
> In his article "Publishing LXD images", Serge Hallyn writes:
> # lxc launch lxc:ubuntu/wily/amd64 w1 # lxc exec w1 -- apt-get -y install upstart-bin upstart-sysv
> 
> However, this does not work, since the wily container does not have an IP address (I have used "wily" as a name instead of "w1"):
> 
> david at kimera:~$ lxc list
> +--------+---------+-----------+------+-----------+-----------+
> |  NAME  |  STATE  |   IPV4    | IPV6 | EPHEMERAL | SNAPSHOTS |
> +--------+---------+-----------+------+-----------+-----------+
> | trusty | RUNNING | 10.0.3.54 |      | NO        |         0 |
> | wily   | RUNNING |           |      | NO        |         0 |
> +--------+---------+-----------+------+-----------+-----------+
> david at kimera:~$ lxc image list
> +-------+--------------+--------+-----------------------+--------+---------+------------------------------+
> | ALIAS | FINGERPRINT  | PUBLIC |      DESCRIPTION      |  ARCH  |  SIZE   |         UPLOAD DATE          |
> +-------+--------------+--------+-----------------------+--------+---------+------------------------------+
> |       | 1a62876f8e08 | no     | Ubuntu wily (amd64)   | x86_64 | 74.51MB | Dec 7, 2015 at 12:32pm (CET) |
> |       | 23f3395b9409 | no     | Ubuntu trusty (amd64) | x86_64 | 64.57MB | Nov 30, 2015 at 6:57pm (CET) |
> +-------+--------------+--------+-----------------------+--------+---------+------------------------------+
> 
> Therefore apt-get naturally fails.
> 
> How can this be accomplished? I am interested in exactly this, a wily container with upstart.
> 
> Thanks,
> David

You may just need to wait a bit until systemd is done configuring eth0.
(Using the newest lxcfs on the host should speed that up)
_______________________________________________
lxc-users mailing list
lxc-users at lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20151207/bf2c01ee/attachment.html>