[lxc-users] lxc-start fails with invalid pid on arm

[Praveen Kumar Verma]

Since both host name(dra7xx) were same, I was not able to differentiate between them.
Now after changing the host name(prav), I can see the container is running.

But I am seeing that there is continuous switching between the host busybox filesystem & busybox filesystem running in container.

/* host busybox, not running in container */
root at dra7xx:~#
/* running in container */
root at prav:~#
root at dra7xx:~#
root at prav:~#
root at dra7xx:~#
root at prav:~#

So due to above, i am not able to enter the commands.

________________________________________
From: lxc-users [lxc-users-bounces at lists.linuxcontainers.org] on behalf of Serge Hallyn [serge.hallyn at ubuntu.com]
Sent: Saturday, April 18, 2015 12:01 AM
To: LXC users mailing-list
Subject: Re: [lxc-users] lxc-start fails with invalid pid on arm

Quoting Praveen Kumar Verma (Praveen.Verma at LntTechservices.com):
> Hi Serge,
>
> Sorry I am not cleared; Please see my answers pointwise:
>
> >>i don't understand what you've done, what you wanted to have happen, or what actually happened.
>
> I took a busybox based filesystem which doesn't have any lxc-container support.

Ah, I see.

> So I downloaded the lxc-1.1.0 package & After cross compiling the lxc package I installed the binaries in busybox file system.
> Our aim is to support linux container on busybox based filesystem. So that we can boot android or busybox over linux container.
>
> >> When you say "I am login as a root in buysbox file system", what do you mean exactly
> I use "root" as a login to busybox file system. Till now I have not created any container. I logged in as a root into busybox file system.
>
> >>what do you mean exactly, is that logged in over lxc-console with the container running?
> No, I havenot created any container till now. After login into busybox filesystem, Now I create a container named "bb" using lxc-create. Now after creating the container, I can see the rootfs present in /var/lib/lxc/bb directory, that means container successfully created.
>
> >> Why did you create the 'root' cgroups by hand?
> We didn't have cgmanger to handle the cgroup so I created a root entry in cgroup.
>
> >>  or what actually happened?
> After doing all above, when I started a container using "lxc-start" it fails with invalid pid. As follows:
>
>        lxc-start 1414573214.442 DEBUG    lxc_conf - conf.c:setup_caps:2139 - capabilities have been setup
>        lxc-start 1414573214.442 NOTICE   lxc_conf - conf.c:lxc_setup:3921 - 'bb' is setup.
>        lxc-start 1414573214.442 NOTICE   lxc_start - start.c:start:1232 - exec'ing '/sbin/init'
>        lxc-start 1414573214.482 NOTICE   lxc_start - start.c:post_start:1243 - '/sbin/init' started with pid '1896'
>        lxc-start 1414573214.482 WARN     lxc_start - start.c:signal_handler:307 - invalid pid for SIGCHLD

This here looks good - the container started.  (The invalid pid msg is innocuous)

Are you after this able to 'lxc-attach -n containername' ?
_______________________________________________
lxc-users mailing list
lxc-users at lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
L&T Technology Services Ltd

www.LntTechservices.com<http://www.lnttechservices.com/>

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.