On Thu, Sep 03, 2020 at 03:27:37PM +0100, Ben Green wrote:
> Hi all,
>
> We are starting to use LXC in production here, after solving our final
> problem (inconsistent and disappearing cgroup space - Thread name
> "Disappearing Cgroups" on this list) completely with the help of Serge
> E. Hallyn.
On Tue, May 19, 2020 at 02:46:34AM -0400, Saint Michael wrote:
> Ubuntu 18.04
> 5.3.0-51-generic
> lxc-start --version
> 4.0.0-devel
> I can no longer start my containers, how do I get back to a version of LXC
> that still works with this kernel?
This should already be fixed in master but I'll try
On Thu, May 14, 2020 at 02:27:30PM -0400, Saint Michael wrote:
> I use the ubuntu
> add-apt-repository ppa:ubuntu-lxc/lxc-git-master
> lxc-start --version
> 4.0.0-devel
I've sent a few fixes just now. Once Stéphane merges them and a new
package has been pushed those issues should hopefully be gone
On Tue, May 19, 2020 at 02:46:34AM -0400, Saint Michael wrote:
> Ubuntu 18.04
> 5.3.0-51-generic
> lxc-start --version
> 4.0.0-devel
> I can no longer start my containers, how do I get back to a version of LXC
> that still works with this kernel?
Hey,
Sorry that was a regression. It is fixed by:
On Thu, May 14, 2020 at 09:13:01AM -0400, Saint Michael wrote:
> I am getting thousands of messages like this in my log, inside the
> container:
> May 14 13:09:38 iowa agetty[12473]: /dev/console: not a character device
> May 14 13:09:48 iowa systemd[1]: console-getty.service: Service hold-off
> ti
On February 28, 2020 8:09:45 PM GMT+01:00, "Serge E. Hallyn"
wrote:
>On Fri, Feb 28, 2020 at 02:34:25PM +0100, Ede Wolf wrote:
>> Hello,
>>
>> do we have any alternatives to classical bridging right now for
>connecting
>> (to) unprivileged containers? Like macvlan or ipvlan?
>>
>> If so, I may
On Tue, Jul 23, 2019 at 01:31:12PM +0200, Tomasz Chmielewski wrote:
> Since around 2019-07-23, lxcfs segfaults randomly on Ubuntu 18.04 servers
> with LXD from snap:
>
> lxcfs[1424]: segfault at 0 ip 7f518f5e4326 sp 7f519da1f9a0 error 4
> in liblxcfs.so[7f518f5d8000+1a000]
>
>
> As a res
Hey everyone,
We're excited to announce another edition of the combined Containers and
Checkpoint/Restore micro-conference at this year's Linux Plumbers
conference in Lisbon, Portugal!
The Containers and Checkpoint/Restore micro-conference at Linux Plumbers
is the opportunity for runtime and kern
On Fri, Apr 12, 2019 at 6:17 PM ITeng A wrote:
> Dear all
>
> Does the current version of LXC 3.0.3 support the new cgroup v2 ?
> I try to run LXC containers with the unified cgroup but containers fail
> to start with these error "
>
> Failed to create directory "/sys/fs/cgroup/unified//lxc/u2
On Sat, Mar 09, 2019 at 10:16:40PM +0300, Andrey wrote:
> Greetings, All.
>
> Saturday, March 9, 2019, 22:11:32 you wrote:
>
> AR> Greetings, All!
>
> AR> Mar 9 22:09:01 ih152926 kernel: [2612590.101781] audit:
> AR> type=1400 audit(1552158541.103:2286):
> AR> apparmor="DENIED" operation="mount
On Sun, Feb 03, 2019 at 09:47:25AM +0100, Stéphane Graber wrote:
> Hi,
>
> Yes, this is normal and as pointed out already, can be tweaked with
> dmesg_restrict.
>
> There was some interest a while back in implementing a logging
> namespace, which would solve this cleanly, but it's never been enou
Hey,
On Tue, Jan 15, 2019 at 12:19:35PM +, Datta, Souvik wrote:
> Hello,
>
>
> I am new to container technology and at present, experimenting with LXC and
> runC. I need to run a system container on an embedded target which has a
> requirement of fast startup time.
>
> In this context, ca
On January 27, 2019 7:47:25 PM GMT+01:00, Bryan Christ
wrote:
>Andrey,
>
>Thanks for the reply. Is there a resource, document, guide that can
>show
>me what the old items were and what the new analogs are? Most of my
>config
>files are from the templates so I added very little. I tried startin
On Fri, Dec 14, 2018 at 11:37 AM Harald Dunkel
wrote:
> Hi folks,
>
> lxc-checkconfig tells me
>
> :
> --- Misc ---
> Veth pair device: enabled, loaded
> Macvlan: enabled, not loaded
> Vlan: enabled, not loaded
> Bridges: enabled, loaded
> Advanced netfilter: enabled, not loaded
> CONFIG_NF_NAT_I
On November 5, 2018 8:12:35 AM GMT+03:00, kemi wrote:
>
>
>On 2018/11/2 下午8:05, Fajar A. Nugraha wrote:
>> On Fri, Nov 2, 2018 at 8:44 AM, kemi wrote:
>>
>>>
>>> thx for your question.
>>> In our case, our customers want to run android games within
>containers on
>>> cloud.
>>>
>>
>> It might b
rently. So resorting to emailing a
> patch ]
>
> We do (afaik) still need something to setup cgroups at login, so recommend
> libpam-cgfs as the first, most highly recommended, means.
>
> Signed-off-by: Serge Hallyn
Acked-by: Christian Brauner
> ---
> content/lxc/getting-
On Mon, Sep 24, 2018 at 03:40:57PM +0200, Tomasz Chmielewski wrote:
> Turns out something changed the permissions on "containers" directory:
Odd, the new storage snapshot api performs an on-disk upgrade but it
shouldn't touch the containers directory...
//cc Stéphane
Christian
>
>
> # lxc stor
On Mon, Sep 24, 2018 at 02:11:38PM +0200, Christian Brauner wrote:
> On Mon, Sep 24, 2018, 14:03 Kees Bakker wrote:
>
> > Same question again: what is the best approach to recover
> > from a container in an ERROR state?
So another thing I would like to see is the current
On Mon, Sep 24, 2018, 14:03 Kees Bakker wrote:
> Same question again: what is the best approach to recover
> from a container in an ERROR state?
>
Please show me the dmesg output. If it is a kernel bug you're hitting
there's nothing that LXD can do to help you.
> This time it happened with Ubu
> Kees Bakker hat am 11. September 2018 um 15:13 geschrieben:
>
>
> Hey,
>
> Every now and then we have one or more containers in state ERROR.
> Is there a clever method to recover from that, other than
> rebooting the LXD server?
>
> Killing the monitor and the forkstart does help. And also
On Mon, Sep 10, 2018 at 01:54:21AM +1200, Richard Hector wrote:
> On 10/09/18 01:40, Christian Brauner wrote:
> > On Mon, Sep 10, 2018 at 01:30:42AM +1200, Richard Hector wrote:
> >> Hi all,
> >>
> >> I have messages like this in the logs on several
On Mon, Sep 10, 2018 at 01:30:42AM +1200, Richard Hector wrote:
> Hi all,
>
> I have messages like this in the logs on several of my (lxc, not lxd)
> containers:
>
> systemd[1]: phpsessionclean.service: Failed to reset devices.list:
> Operation not permitted
>
> systemd[1]: run-user-1000.mount:
On Sun, Sep 09, 2018 at 09:31:02AM +0300, Amir Goldstein wrote:
> On Sun, Sep 9, 2018 at 4:31 AM Christian Brauner wrote:
> >
> ...
> > > [cc: overlayfs developers]
> > >
> > > Hi Stéphane!
> >
> > Hey Amir,
> >
> > I'm one of
On Sat, Sep 08, 2018 at 10:41:41AM +0300, Amir Goldstein wrote:
> On Sat, Sep 8, 2018 at 8:00 AM Stéphane Graber wrote:
> >
> > On Mon, Aug 13, 2018 at 12:10:15PM -0400, Stéphane Graber wrote:
> > > Hello,
> > >
> > > This year's edition of the Linux Plumbers Conference will once again
> > > have
On Thu, Aug 16, 2018 at 09:07:16PM +0200, Dr. Todor Dimitrov wrote:
> A follow-up: I assume the same applies to sys:mixed vs. sys:rw, correct?
Yes. Newever LXC versions will always set sys:rw for unpriv containers.
Christian
>
> Todor
>
> > On 23. May 2018, at 19:09, Christ
On Wed, Aug 15, 2018 at 11:49:40AM +, Tomasz Chmielewski wrote:
> # lxc list
> cannot perform readlinkat() on the mount namespace file descriptor of the
> init process: Permission denied
Where is this error coming from? It's not from LX{C,D}
What does lxc info show?
>
> # dmesg -c
> [ 1554.5
that he is on board.
In case you were wondering who currently maintains what. For LXD we have
Serge Hallyn, Christian Brauner, Stéphane Graber, Free Ekanayaka, Tycho
Andersen, and Mike Mccracken. For LXC we have Serge Hallyn, Christian
Brauner, Stéphane Graber, Dwight Engen, and Wolfgang Bumille
On Mon, Jul 23, 2018 at 05:12:09PM +0700, Fajar A. Nugraha wrote:
> On Mon, Jul 23, 2018 at 5:08 PM, Pierre Couderc wrote:
>
> > Where can I find a howto for lxd on a an ultramobile with wifi only ?
> >
> > I find some posts aged 2014 and more modern posts saying it is not
> > possible with wifi.
templates"
> as a dependency, even though "lxc-utils" does[should] not. Since "lxc"
> is now branded as a transitional package => lxc-utils.
That's a packaging call that Stéphane needs to make.
>
>
> Adrian Pepper
> arpep...@uwaterloo.ca
>
On Mon, Jul 16, 2018 at 08:24:09AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> is there a way to tell lxc-create to support a custom(!) UID and
> GID map via lxc.idmap? Each container should get its own mapping.
>
> Problem behind this is that some containers may affect each other
> by exceeding
On Thu, Jul 05, 2018 at 01:06:29PM -0400, Chaetoo3 wrote:
> > You mean it wouldn't change from "my binary --with --args" to "[lxc
> > monitor]?
>
> Yes, exactly like that.
>
> It seems to me that proc stat file is for machine parsing, but is not
> so convenient for machine parsing. I do not kno
On Mon, Jul 09, 2018 at 02:08:03AM +1200, Richard Hector wrote:
> Hi all,
>
> I'm seeing this in auth.log on an lxc host (no lxd).
>
> "PAM-CGFS[xxx]: Failed to get list of controllers"
>
> This is on a host I didn't set up; I've inherited maintenance for it,
> and recently added logcheck.
>
>
On Wed, Jul 04, 2018 at 03:23:19PM -0400, Chaetoo3 wrote:
> Hi!
>
> I try to use the liblxc start() API from my process and it worked, but
> I notice it would not set the process name for the container process
> as it would do from the lxc-start command line. Instead the container
> process staye
On Thu, Jun 28, 2018 at 11:07:38AM +0530, Emmanuel Livingstone wrote:
> For now to overcome this issue, we've added a patch to an internal mirror
> of lxc debian repo https://anonscm.debian.org/git/pkg-lxc/lxc.git
> If you guys think adding a config parameter to not mask out the isolcpus in
> cpuse
On Tue, Jun 26, 2018 at 08:44:09AM +1000, Tony Lewis wrote:
> On 25/06/18 21:22, Christian Brauner wrote:
> > On Sat, Jun 23, 2018 at 11:19:17PM +1000, Tony Lewis wrote:
> > > Host is Debian Stretch, 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1
> > > (2018-05-07) x
On Sat, Jun 23, 2018 at 11:19:17PM +1000, Tony Lewis wrote:
> I am trying to use FUSE in a container, namely bup. I get the following
> error:
>
> fusermount: mount failed: Operation not permitted
>
> The most recent instructions for this seem to be at
> http://blog.forshee.me/2016/02/container-
-d alpine -r edge -a amd64
and then take a look at the loop file that got created. This is the
format we support.
Christian
>
> Thanks,
> Todor
>
> > On 15. Jun 2018, at 17:50, Christian Brauner wrote:
> >
> > On Fri, Jun 15, 2018 at 05:02:50PM +0200, Dr. Todor
ts root file system with the host.
> "
>
> Todor
>
> > On 15. Jun 2018, at 16:39, Christian Brauner wrote:
> >
> > On Fri, Jun 15, 2018 at 10:28:34AM +0200, Dr. Todor Dimitrov wrote:
> >> Hallo,
> >>
> >> is it possible to use an image file with
On Fri, Jun 15, 2018 at 10:28:34AM +0200, Dr. Todor Dimitrov wrote:
> Hallo,
>
> is it possible to use an image file with “lxc.rootfs.path” for an
> unprivileged container? If possible, is it necessary to have the
> correct file ownerships within the image or are these automatically
> adjusted on
On Tue, Jun 05, 2018 at 02:25:52PM +0200, Mohamed LADGEM wrote:
> Hi,
>
> Since few days, I'm struggling with lxc as unpriveleged user to start
> an alpine without success. I am running 2.1.1 from ganto/lxc repo.
>
> I ran lxc-start -n test --logpriority=DEBUG --logfile=/tmp/log_lxc
> Could you h
On Mon, Jun 04, 2018 at 08:47:28PM -0400, Saint Michael wrote:
> I am struggling with adding LXC 3.0 to the latest Fedora Server 27.
> Also, in Fedora, the containers do no start automatically. I think I am
> missing some step in the system configuration. Any idea how to add LXC 3.0
> to Fedora and
On Wed, May 23, 2018 at 06:13:02PM +0200, Dr. Todor Dimitrov wrote:
> Hallo,
>
> is there any security benefit of using proc:mixed inside an unprivileged
> container? Or does proc:rw deliver the same level of isolation?
There's no security benefit for unprivileged containers. They can't
change /
Hey everyone,
We've recently discovered that gcc-8 likes to complain (pointlessly
about non-bugs) a lot when compiling LXC on ArchLinux. This breaks the
build process. We have a set of patches that should fix this. They are
all already backported to at least stable-3.0:
ccd42a31440f584a82bd8aa1f6
On Sat, Apr 07, 2018 at 10:11:58PM +0300, Mihamina RAKOTOMANDIMBY wrote:
> On 4/7/18 5:54 PM, Christian Brauner wrote:
> > 2. **Important** distrobuilder is the new way of creating machine/system
> > container images
> > The templates have been replaced by
On Thu, Mar 29, 2018 at 09:22:07AM -0400, Ray Jender wrote:
> So in Ubuntu 16.04.4 I created 4 LXD containers using LXC. From the host I
> created the first container then did $ lxc copy containter1 container2 , 1
> to 3 and 1 to 4.
>
> It was a challenge for me to make them accessible from the o
On Fri, Mar 23, 2018 at 06:13:15AM -0400, Andrew Cann wrote:
> Hello,
>
> The folowing sycall is failing when called on a Travis-CI build machine.
>
> clone(..,
> CLONE_FILES |
> CLONE_IO |
> CLONE_SIGHAND |
> CLONE_VM |
> CLONE_SYSVSEM |
> CLON
On Sun, Mar 25, 2018 at 05:23:21PM +, Avadhut Bhangui wrote:
> Hello,
> I have an ubuntu system. i login to the device as root user. I have two LXC
> containers created using the busbox template. One is privileged and other one
> is unprivileged.
> I want to ensure that when a USB device is c
On Tue, Mar 27, 2018 at 10:12:15AM -0400, Eric Wolf wrote:
> One of my containers is shutting down seemingly randomly. I'm trying
> to figure out why, but so far all I can find in syslog is systemd[1]:
> Received SIGRTMIN+3. which seems to be related to the LXC/LXD stop
> command, but I can't find
On Tue, Mar 27, 2018 at 11:00:01AM -0500, Ronak Desai wrote:
> Hi,
>
> I came a cross a problem where if the containers are running then it
> affects the unmount process of the system's mount points. I am not
> using these mount points as shared partitions with container.
>
> For example, I am us
Hey everyone,
LX{C,FS,D} upstream here. :)
I'm sorry to ping you all at once in this mail and I seriously hope I only
added actual package maintainers for LXC based projects in their respective
distros to this mail. If not I'm genuinely sorry to have banged on your door
(or rather inbox) on a Sat
On Sat, Mar 31, 2018 at 02:50:00PM +0300, Mihamina RAKOTOMANDIMBY wrote:
> Hello,
>
> Running LXC 3 on Archlinux, after having buit for LXC with "distrobuild
> build-lxc [...]": what is the next step to register the new container and
> start it?
So that's simply (this assumes LXC 3.0):
lxc-creat
On Fri, Mar 23, 2018 at 11:49:08AM +0100, ales drtik wrote:
> Hi,
> i converted LXC conf to xml by:
>
> lxcuser@blade1:~/.local/share/lxc/test_deb$ virsh -c lxc:///
> domxml-from-native lxc-tools /home/lxcuser/.local/share/lxc/test_deb/config
>
>
> test_deb
> cce77799-89fd-41fd-99c1-101e00
On Thu, Mar 01, 2018 at 12:06:59AM -0500, Saint Michael wrote:
> I want to use Fedora 27 as a container. Supposed I install a physical
> machine with Fedora, how do I convert it to a container?
Stéphane added a new binary to LXD called lxd-p2c
( https://github.com/lxc/lxd/tree/master/lxd-p2c ) whi
On Thu, Mar 01, 2018 at 03:48:06AM +0300, Andrey Repin wrote:
> Greetings, Christian Brauner!
>
> > And if that makes you
> > more likely to read it: there are asciicasts. :)
>
> 410 Gone
Oha, let me fix this :) Thanks!
Christian
>
> :(
>
>
>
Hey everyone,
Yet another blogpost about LXC 3.0 development. This time we'd like to
tell you what happens to the pam_cgfs.so pam module that we used to ship
with LXCFS. You can read the details here:
https://brauner.github.io/2018/02/28/lxc-includes-cgroup-pam-module.html
We're near the finish
Hey everyone,
This is another update about the LXC 3.0 development. Instead of copying
and pasting what I wrote on my blog here I'm going to be lazy and please
ask you to read:
https://brauner.github.io/2018/02/27/lxc-removes-legacy-template-build-system.html
This should give you an idea what we
On Tue, Feb 20, 2018 at 07:17:42PM +0100, Dirk Geschke wrote:
> Hi Christian,
>
> > > Does this mean that lxc 3.0 is systemd-only?
> >
> > No!
> >
> > This has no effect whatsoever on what init system you are running. This
> > is completely orthogonal and to some extent always has been. In fact,
On Tue, Feb 20, 2018 at 13:04:00PM +0100, Harald Dunkel wrote:
> Does this mean that lxc 3.0 is systemd-only?
No!
This has no effect whatsoever on what init system you are running. This
is completely orthogonal and to some extent always has been. In fact,
we've become even more agnostic wrt to w
Hey everyone,
This is another update about the development of LXC 3.0. As of yesterday
the cgmanager and cgfs cgroup drivers have been removed from the
codebase. In the good long tradition of all LXC projects to try our
hardest to never regress our users and to clearly communicate invasive
changes
> Date: Thu, 15 Feb 2018 13:05:44 -0500 (EST)
> From: Adrian Pepper
> To: lxc-users@lists.linuxcontainers.org
> Subject: [lxc-users] Migrating a rootfs back-and-forth lxc 2.0 <=> 3.0
>
> Should one expect to encounter subtle (or perhaps not-so-subtle)
> problems if one takes the rootfs of a simpl
> Date: Tue, 13 Feb 2018 00:32:36 +0300
> From: Andrey Repin
> To: Sean McNamara , All
>
> Subject: Re: [lxc-users] LXC master: Legacy Config Items Have Been Removed
>
> Greetings, Sean McNamara!
>
> > For LXD, is it true that the only potential impact is if you use
> > lxc.raw in a config or
Hey everyone,
We've been making good progress on the way to 3.0 for all affected
projects under the LXC umbrella. One of the more invasive steps we have
undertaken yesterday is to remove the support for all legacy
configuration items from the LXC master branch. We have announced this
back when LXC
Hey everyone,
We are currently in the process of cleaning up the lxc issue list on
Github ( https://github.com/lxc/lxc/issues ). This may cause some issues
to be closed that you still consider relevant. Please do not take this
as a slight. We're mainly doing this because a bunch of those issues ha
> Date: Fri, 2 Feb 2018 01:52:09 +0200
> From: Eytan Heidingsfeld
> To: lxc-users@lists.linuxcontainers.org
> Subject: [lxc-users] Using lxc.namespace.net in unprivileged containers
>
> Hi,
> I'm trying to use the new lxc.namespace.net config in an unprivileged
> container (using idmapping)
> The
On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > Hi Serge,
> >
> > > > I am a little bit clueless, I have several systems running with
> > > > Debian and unprivileged LXC. But newer systems won't start new
> > > > con
() which does not run
pthread_atfork() handlers. If push comes to shove we might just go for doing
the clone() syscall directly via syscall(SYS_clone, ...).
Serge, please take a look at https://github.com/lxc/lxc/pull/2034 and
see whether that is acceptable to you. :)
Christian
>From 3b52c88ce5
On Wed, Dec 13, 2017 at 09:22:11AM -0600, Serge Hallyn wrote:
> Quoting Christian Brauner (christian.brau...@mailbox.org):
> > On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > > > Hi
On Wed, Dec 13, 2017 at 01:35:01PM +0100, Christian Brauner wrote:
> On Wed, Dec 13, 2017 at 12:54:04PM +0100, Christian Brauner wrote:
> > On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote
On Wed, Dec 13, 2017 at 12:54:04PM +0100, Christian Brauner wrote:
> On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > > Hi Serge,
> > >
> > > > > I am a little bit clu
On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > Hi Serge,
> >
> > > > I am a little bit clueless, I have several systems running with
> > > > Debian and unprivileged LXC. But newer systems won't start new
> > > > con
On Wed, Oct 25, 2017 at 11:45:52AM +0200, Sedat Dilek wrote:
> [ Please CC me - I am not subscribed to lxc-users and debian-kernel MLs ]
>
> Hi,
>
> I am playing with LXC and OverlayFS.
>
> The Debian-kernel shipped with stretch64 fails when using lxc-copy for
> a snapshot.
> Later I tried the l
On Wed, Oct 04, 2017 at 03:35:08PM -0400, Adrian Pepper wrote:
> Does mentioning lxc.pivotdir really need to be a fatal error? Currently
> it seems fatal to the degree that "lxc-ls -f" does not show the
> container at all, not RUNNING and not STOPPED.
As I said in my previous mail, we've merged a
On Wed, Oct 04, 2017 at 09:35:25AM -0500, Serge Hallyn wrote:
> Quoting Kees Bos (cornelis@gmail.com):
> > I'm not using it, but do expect the extra args:
> >
> > while [ {{ '${#@}' }} -gt 3 ] ; do
> > ...
> > shift
> > done
> >
> > It might be that some users will need the last extra a
On Wed, Oct 04, 2017 at 06:53:16PM -0500, Serge Hallyn wrote:
> agreed to both, lxc-update-config should delete it, and it should be
> (initially the only) member of a (new) group of keys to ignore, bc
I sent a branch [1] that does:
- removes lxc.kmsg and lxc.pivotdir from config files if deteced
On Thu, Jul 13, 2017 at 12:27:52PM +0200, Christian Brauner wrote:
> On Wed, Jul 12, 2017 at 04:25:54PM -0400, Stéphane Graber wrote:
> > On Wed, Jul 12, 2017 at 01:44:13PM -0600, Joshua Schaeffer wrote:
> > > I'm wondering what the best/recommended approach is to adding a
On Wed, Jul 12, 2017 at 04:25:54PM -0400, Stéphane Graber wrote:
> On Wed, Jul 12, 2017 at 01:44:13PM -0600, Joshua Schaeffer wrote:
> > I'm wondering what the best/recommended approach is to adding a second disk
> > to a container. I'm using LXD 2.15 on Ubuntu 16.04. As an example I have a
> > c
- Forwarded message from Javier López Sánchez -
Date: Mon, 24 Apr 2017 14:04:34 +0200
From: Javier López Sánchez
To: christian.brau...@ubuntu.com
Subject: Managing tarballs in lxd
Hello Christian, I don't know where to publish this. To help anybody who
need, this is how I make backups a
Hi Detlef,
Now we're getting somewhere. :)
On Wed, Jan 11, 2017 at 03:59:21PM +0100, Detlef Vollmann wrote:
> Hi Christian,
>
> thank you for replying!
>
> On 01/09/17 17:35, Christian Brauner wrote:
> > Thanks for the info. I'm a little confused.
> Sorry abou
Hi Detlef,
I sent a branch against lxc (https://github.com/lxc/lxc/pull/1381) which removes
the c->is_defined(c) check.
Thanks!
Christian
On Wed, Jan 11, 2017 at 04:10:53PM +0100, Christian Brauner wrote:
> Hi Detlef,
>
> Now we're getting somewhere. :)
>
> On Wed, Jan
Hi,
Thanks for the info. I'm a little confused.
On Thu, Jan 05, 2017 at 01:31:28PM +0100, Detlef Vollmann wrote:
> On 01/01/17 14:14, Christian Brauner wrote:
> > Hm, works for me. I can just start containers fine where the
> > configuration file is located somewhere
oks like
>
> commit 359467743d707d08fda029fa6e957a93bc8dc7ef
> Author: Christian Brauner
> Date: Fri Oct 14 15:27:24 2016 +0200
>
> tools: better error reporting for lxc-start
>
> which added a check for "!c->is_defined(c)"
>
> Christian?
>
>
Hi, can you please open a bug on https://github.com/lxc/lxc ?
Please specify your operating system version and how to reproduce.
Thanks. :)
Christian
On Wed, Nov 09, 2016 at 01:33:55AM -0500, Saint Michael wrote:
> It was working fine until a week ago.
> I have two sites, it happened on both, so
On Tue, 10 Nov 2015 14:19:41 +0900, Tomasz Chmielewski :
> lxc-destroy may be destroying wrong containers!
>
> To reproduce:
>
> 1) have a container you want to clone - here, testvm012d:
>
> # lxc-ls -f
> NAMESTATEIPV4
> IPV6 GROUPS AUTOSTART
> -
On Tue, Nov 10, 2015 at 10:02:00PM +0900, Tomasz Chmielewski wrote:
> On 2015-11-10 20:29, Christian Brauner wrote:
>
> >This may not have something to do with lxc-destroy but with how clones
> >work. Can
> >you only proceed up to step 2) you listed:
> >
> >
Hm, both work without a problem when I try it. safe_mount() is a function that
has been added recently to protect containers against symlinks. Specifically, it
prevents two things:
1. do not allow mounts to paths containing symbolic links
2. do not allow bind mounts from relative
Hi,
it seems that lxcfs v0.10 is out but there is no corresponding source package on
the download site from lxcfs on linuxcontainers.org. Would be good for distros
that get their source package from there. :)
Christian
signature.asc
Description: PGP signature
___
Hallyn
> To: LXC users mailing-list
> Subject: Re: [lxc-users] lxcfs 0.9
>
> Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > Hello,
> >
> > it seems on Github lxcfs 0.9 is out for quite a while now but there has
> > been no
> > sour
Hello,
it seems on Github lxcfs 0.9 is out for quite a while now but there has been no
source package uploaded to linuxcontainers.org. Is this on purpose? If not it
would be great if you could put it up so I can update the corresponding arch
package.
Best,
Christian
pgpFjSX2dD8IB.pgp
Descriptio
Just a heads up,
4.1-rc4 includes both required patches:
(1)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=820f9f147dcce2602eefd9b575bbbd9ea14f0953
(2)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cd4a40174b71acd021877341684d8bb1dc8ea4ae
Hello,
it seems that the two patches which were accidently removed from 4.0.2 which are
required to prevent a kernel panic when starting unprivileged lxc containers are
still not present in 4.0.3 and 4.0.4. I still get a total freeze when starting
an unprivileged container on a 4.0.4 kernel. Accid
Hello,
When I follow the journal output of systemd with
journalctl -f
I see an endless stream of warnings thrown by cgmanager. They are all
the same and appear for every operation I do where cgmanager is involved:
cgmanager[324]: Could not get password database information for UID
o
When I follow the journal output of systemd with
journalctl -f
I see an endless stream of warnings thrown by cgmanager. They are all
the same and state:
cgmanager[324]: Could not get password database information for UID
of current process: User "???" unknown or no memory to allocate
Hello,
is it currently possible to use macvlan interfaces with unprivileged
containers?
Best,
Christian
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
For the ones unfamiliar with patching software, here is are links to my
Google Drive with patched systemd-versions for Fedora 21 and Rawhide,
and Archlinux:
Fedora:
(1) systemd
https://drive.google.com/file/d/0B_UAut69TSAiTmI3SnN4TzRTaXM/view?usp=sharing
(2) systemd-libs
https://drive.google.com
I think I can help here. Systemd-based unprivileged containers will only work
properly with systemd compiled from git (master) or systemd 218 patched with:
From: Lennart Poettering
Date: Thu, 8 Jan 2015 23:12:16 +0100
Subject: core: make EPERM errors when applying OOM adjustment for forked
proce
> On Sat, Feb 07, 2015 at 06:44:31PM +0100, Christian Brauner wrote:
> > When an init such as systemd mounts a folder as a tmpfs during startup and
> > the
> > lxc defines a bind-mount on the same folder in the containers config it
> > will be
> > overmounted
When an init such as systemd mounts a folder as a tmpfs during startup and the
lxc defines a bind-mount on the same folder in the containers config it will be
overmounted on container startup. Here is an example. Create an archlinux (or
fedora) container with:
sudo lxc-create -t archlinux -n a
Hello,
is there a list of all possible options that an lxc bind-mount entry
lxc.mount.entry
it seems they are not necessarily the same as for fstab. E.g.
create=dir
create=file
I'm also unclear about "optional" and "none". Such a list would be
really good.
Best,
Christian
pgpSiQ
-EPERM && err != -EACCES) {
*error = EXIT_OOM_ADJUST;
return -errno;
}
works
On Thu, Feb 05, 2015 at 10:51:26PM +0100, Christian Brauner wrote:
> On Thu, Feb 05, 2015 at 10:19:15PM +0100, Christian Brauner wrote:
On Thu, Feb 05, 2015 at 10:19:15PM +0100, Christian Brauner wrote:
> On Thu, Feb 05, 2015 at 10:14:37PM +0100, Christian Brauner wrote:
> > On Thu, Feb 05, 2015 at 09:25:12PM +0100, Christian Brauner wrote:
> > > I hope so, I've just patched my systemd source
1 - 100 of 119 matches
Mail list logo
