Hi Fajar,
> > $ grep -v ^# .local/share/lxc/lxc-geschke/config
> >
> > lxc.include = /usr/local/share/lxc/config/debian.common.conf
> > lxc.include = /usr/local/share/lxc/config/debian.userns.conf
> > lxc.arch = x86_64
> >
> > lxc.include = /usr/local/share/lxc/config/debian.common.conf
> >
On Sun, Oct 18, 2015 at 9:42 PM, Dirk Geschke wrote:
> Hi Fajar,
>
>> > Do you have an idea, what's going wrong?
>>
>>
>> Well, for one thing, listing the relevant part of your setup should
>> help. That includes what your container config looks like, including
>> the "few
Hi Fajar,
> > Do you have an idea, what's going wrong?
>
>
> Well, for one thing, listing the relevant part of your setup should
> help. That includes what your container config looks like, including
> the "few bind mounts".
ah, yes, I thought it was only minor issue to fix it, so I skipped
Hi Fajar,
> The log files are attached, maybe you can see something?
i was too fast, now they are attached, sorry...
Dirk
--
+--+
| Dr. Dirk Geschke / Plankensteinweg 61/ 85435 Erding|
| Telefon:
On Fri, Oct 16, 2015 at 6:17 PM, Dirk Geschke wrote:
> Hi Fajar,
>
>> > Yes, it exists. But I think it is only used, if the containers are
>> > started by the user root?
>>
>> So you see, first it mounts the rootfs, then other supporting files/dirs.
>>
>> My guess is you
On Fri, Oct 16, 2015 at 1:16 PM, Dirk Geschke wrote:
>> > That works fine with 1.1.2, but not with 1.1.4...
>>
>> su (and sudo) by default does not assign a new tty. So your user ends
>> up with a tty owned by root, thus the tty-related errors.
>
> yes and this works with
Hi Fajar,
> > not lxd, it's plain lxc from linuxcontainers.org and compiled the
> > same way as 1.1.2. To start I use as part of init-script, started
> > by root:
> >
> > /usr/local/bin/cgm create all ${CONTAINER}
> > /usr/local/bin/cgm chown all ${CONTAINER} `id -u $user` `id -g $user`
>
Please keep the list in to/cc
On Fri, Oct 16, 2015 at 3:17 PM, Dirk Geschke wrote:
> Hi Fajar,
>
>> > I'm a little bit irritated, shouldn't it be something like
>> >
>> > /home/${USER}/.local/share/lxc/${CONTAINER}/rootfs
>> >
>> > for an unprivileged user?
>>
>> What is
On Fri, Oct 16, 2015 at 4:10 PM, Dirk Geschke wrote:
>> Does /usr/local/lib/lxc/rootfs/ exist? It should be the path used to
>> temporary mount rootfs (/usr/lib/x86_64-linux-gnu/lxc in ubuntu
>> package)
>
> Yes, it exists. But I think it is only used, if the containers are
>
Hi Fador,
> Please keep the list in to/cc
oops, I thought the list was included...
> > oh, it even does not run if I login as this unprivileged user
> > via ssh, still the same error:
> >
>
> You should've mentioned this earlier :)
I thought, I mentioned it. I was just suprised, that it works
Hi all,
I have unprivileged containers running with lxc-1.1.2. They are
started by a normal, non-root user and it works. But today I
tried to start them with lxc-1.1.4 and it fails:
WARN: could not reopen tty: Permission denied
newuidmap: write to uid_map failed: Operation not permitted
Hi Dirk,
On Thu, Oct 15, 2015 at 09:22:25PM +0200, Dirk Geschke wrote:
> Hi all,
>
> I have unprivileged containers running with lxc-1.1.2. They are
> started by a normal, non-root user and it works. But today I
> tried to start them with lxc-1.1.4 and it fails:
>
>WARN: could not reopen
Hi Tycho,
> How are you starting these (hand-built lxd?). lxc 1.1.2 => 1.1.3
> reverted an ABI break which could cause some of these problems,
> perhaps you're hitting that somehow?
not lxd, it's plain lxc from linuxcontainers.org and compiled the
same way as 1.1.2. To start I use as part of
13 matches
Mail list logo