Lucid as LTS must support containers both as host and as hoster.
Not forfeiting that requirement will have huge impact on Ubuntu
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Summary changed:
- LXC does not work with lucid host and lucid container
+ Lucid fails to host and to
This is how I got it working :
http://blog.bodhizazen.net/linux/lxc-configure-ubuntu-lucid-containers/
--
LXC does not work with lucid host and lucid container
https://bugs.launchpad.net/bugs/512200
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I got it working, with a lot less tweaking then you posted on the forums
sweetsinse.
I will work through my notes and post an update ASAP. Basically you do
not need to worry about udev , just set up your devices and edit a few
system files.
Personally I use a static IP on both the host node and i
bodhi.zazen, im not sure if ubuntu has the latest lxc-* tools, the -d
problem you having could be related to that, because i run all my
containers with that option. however, i have noticed my container's (i
can't confirm this for ubuntu based containers yet) networking does not
come up right away
Thomas Bechtold and friends, the lxc-ps command i think is buggy, and
the -n flag doesnt work, try using --name instead. the output you are
seeing is NOT inside the container, it is the same as what you would see
if you simply typed ps. if the process was running in a
container/cgroup you would s
Normally you would enter the container with lxc-console -n ubuntu ,
however it is not working for me as of yet with a lucid container.
Your config file looks very very scant, that is probably about as
minimal as you can get, what else did you do teo set up your container ?
You need to do a bunch o
i used a config file now with the following content:
lxc.utsname = ubuntu
lxc.rootfs = /var/lib/lxc/ubuntu/root/
When i start the container with:
# lxc-start -n ubuntu -f /var/lib/lxc/ubuntu/config
nothing happens. But:
# lxc-info -n ubuntu
'ubuntu' is RUNNING
# lxc-ps -n ubuntu
CONTAINER
to elaborate on the "resource busy" issue... you need to remove/kill the
running processes from the cgroup in order to remove the folder.
view the tasks with:
$ cat /cgroup/ubuntu-lucid/tasks
$ kill -15
most processes should die, unless it was pid one in the container, then
it will need a kil
also this probably should be handled more gracfully on lxc-*'s part, but
the "resource busy" is a consequence of killing the lxc-start process,
and thus the cgroups dont get cleanup up properly. make sure you kill
the process lxc-start STARTED, i.e. /sbin/init (it will be the pid+1 of
lxc-start),
I also have this problem.
I build a container with debootstrap --variant minbase
I then confirmed the files in rootfs.lucid/dev were present and had the
appropriate permissions.
I wrote a basic config defining the network, container name, root , etc
The container starts but does not mount proc
there could be other problems, but you need to define a config file with
lxc-create (the -f option). specifically you need the option:
lxc.rootfs =
to be defined. otherwise, the rootfs will be the shared with the host.
anything that is not defined in the config file is shared with the host
(ne
11 matches
Mail list logo
