Does your busybox include "init" applet? Does it print "init" (among lots of other things) when you run "busybox" without arguments?
-- Fajar On Thu, May 21, 2015 at 1:23 AM, SIVA SUBRAMANIAN.P <psiv...@gmail.com> wrote: > Thanks Fajar, > Now I'm able to configure statically linked busybox to get rid of warnings, > but init applet error exists. > > On Mon, May 18, 2015 at 4:44 PM, Fajar A. Nugraha <l...@fajar.net> wrote: >> >> Read the messages >> >> (1) >> > /usr/share/lxc/templates/lxc-busybox: line 182: file: command not found >> >> you don't have the necessary programs on your host (i.e. you don't >> have "file", usually installed as "/usr/bin/file"). >> >> (2) >> > warning : busybox is not statically linked. >> > warning : The template script may not correctly >> >> your busybox is not statically linked. On ubuntu, you'd need the >> "busybox-static" package. >> >> (3) >> > # lxc-start --name u1 >> > init: applet not found >> >> This might be the result of (2), your busybox does not recognize >> "init" as an applet that it handles. Again, on ubuntu, using >> "busybox-static" should work. >> >> Are you using your own self-compiled busybox? If yes, there are >> options during compile time to enable static linking as well as >> selecting which applets to enable. >> >> -- >> Fajar >> >> On Tue, May 19, 2015 at 3:02 AM, Sivasubramanian Patchaiperumal >> <sivasubramanian.patchaiperu...@lnttechservices.com> wrote: >> > Hi, >> > I'm trying to create and run busybox container, but facing below error. >> > # lxc-create --template=busybox --name=u1 >> > /usr/share/lxc/templates/lxc-busybox: line 182: file: command not found >> > warning : busybox is not statically linked. >> > warning : The template script may not correctly >> > warning : setup the container environment. >> > chmod: /var/lib/lxc/u1/rootfs/bin/passwd: No such file or directory >> > setting root password to "root" >> > Failed to change root password >> > 'dropbear' ssh utility installed >> > >> > # lxc-start --name u1 >> > init: applet not found >> > lxc-start: lxc_start.c: main: 342 The container failed to start. >> > lxc-start: lxc_start.c: main: 346 Additional information can be obtained >> > by >> > setting the --logfile and --logpriority options. >> > >> > Regards, >> > Sivasubramanian >> > Skype: sivasubramanian.patchaiperumal >> > >> > L&T Technology Services Ltd >> > >> > 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. >> > >> > >> > _______________________________________________ >> > lxc-users mailing list >> > lxc-users@lists.linuxcontainers.org >> > http://lists.linuxcontainers.org/listinfo/lxc-users >> _______________________________________________ >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
