This is now also documented on https://linuxcontainers.org/lxc/getting-
started/.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Yes, I probably need unprivileged containers (not sure why, though). I
wish that lxc-create could provide a better command line guide than
searching on the internet and some help about what container do I need.
I just need isolated Linux environment to package my Python script so
that it is
Two steps are needed to support completely unprivileged containers.
Suggestions about the best (safe) way to make those easier are very
welcome.
We can definately do better about the id mapping case. I'm not sure about
the lxc-usernet one, but it's definately worth discussing.
status: triaged
Sorry, I don't quite understand your questions. What do you mean by
running under the root? What is the problem at this point? If
you're getting an error creating unprivileged containers (which are
created/started without becoming the root user), see Basic unprivileged
usage at
Cool. Is there a way to use default template for current operating
system? I don't want to know about templates yet, so I'd be happy with
whatever default is there (I am not sure what a rootfs in container is
and if I want it).
Also, could it be the problem that I am not running under the root?
You need to specify a template for the container to create. For
instance,
lxc-create -t download -n buildbox -- -d ubuntu -r trusty -a amd64
In newer releases, you do get a better error message:
# lxc-create -n b1
A template must be specified.
Use none if you really want a container without a
6 matches
Mail list logo
