this should be fixed by the fix to bug 1554269.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
Unprivileged nested Xenial container will not start inside a
privileged
this should be fixed by the fix to bug 1554269.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
Unprivileged nested Xenial container will not start inside a
privileged Xenial
Hi - there should be a way, we just need to get sudo running the pam
module.
Perhaps libpam-cgfs should be added to /etc/pam.d/common-session-
noninteractive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi - there should be a way, we just need to get sudo running the pam
module.
Perhaps libpam-cgfs should be added to /etc/pam.d/common-session-
noninteractive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Serge,
Thanks for working with me on this.
So it does work when I ssh into the privileged container as user ubuntu
and then start the unprivileged container.
I'm guessing there may be no way to start the unprivileged container
from lxc-attach like I want to, right?
Here is the output you
Hi Serge,
Thanks for working with me on this.
So it does work when I ssh into the privileged container as user ubuntu
and then start the unprivileged container.
I'm guessing there may be no way to start the unprivileged container
from lxc-attach like I want to, right?
Here is the output you
Quoting Christopher Townsend (christopher.towns...@canonical.com):
> I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
> didn't know this existed. However, it didn't help.
>
> As you say, I can create unprivileged containers as user ubuntu, I just
> can't start them. Are
Quoting Christopher Townsend (christopher.towns...@canonical.com):
> I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
> didn't know this existed. However, it didn't help.
>
> As you say, I can create unprivileged containers as user ubuntu, I just
> can't start them. Are
I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
didn't know this existed. However, it didn't help.
As you say, I can create unprivileged containers as user ubuntu, I just
can't start them. Are you able to start unprivileged containers as user
ubuntu? If so, how are you
I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
didn't know this existed. However, it didn't help.
As you say, I can create unprivileged containers as user ubuntu, I just
can't start them. Are you able to start unprivileged containers as user
ubuntu? If so, how are you
I'm running 4.4.0-10-generic #25-Ubuntu with lxc version
2.0.0~rc5-0ubuntu1 , and the privileged container has:
lxc.include = /usr/share/lxc/config/nesting.conf
in the configuration file. This is a clean VM with no ppas installed.
Inside the privileged container (also xenial with no ppas), I
I'm running 4.4.0-10-generic #25-Ubuntu with lxc version
2.0.0~rc5-0ubuntu1 , and the privileged container has:
lxc.include = /usr/share/lxc/config/nesting.conf
in the configuration file. This is a clean VM with no ppas installed.
Inside the privileged container (also xenial with no ppas), I
Sure, here is the requested info:
$ uname -a
Linux Slave1 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:33:19 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Sure, here is the requested info:
$ uname -a
Linux Slave1 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:33:19 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I'm having a problem as well, but a different one in recent xenial
kernels.
Can you tell us the release and kernel (uname -a) of your host?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi,
I'm having a problem as well, but a different one in recent xenial
kernels.
Can you tell us the release and kernel (uname -a) of your host?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543697
I have version 2.0.0~rc5-0ubuntu1 on both the Xenial host and Xenial
privileged container installed. I have rebooted the host and have also
stopped and restarted the privileged container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have version 2.0.0~rc5-0ubuntu1 on both the Xenial host and Xenial
privileged container installed. I have rebooted the host and have also
stopped and restarted the privileged container.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Please show which version you are currently using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
Unprivileged nested Xenial container will not start inside a
privileged Xenial
Please show which version you are currently using?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
Unprivileged nested Xenial container will not start inside a
This still doesn't seem fixed. I've attached the latest debug log.
** Attachment added: "start_test.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+attachment/4588355/+files/start_test.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This still doesn't seem fixed. I've attached the latest debug log.
** Attachment added: "start_test.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+attachment/4588355/+files/start_test.out
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package lxc - 2.0.0~rc5-0ubuntu1
---
lxc (2.0.0~rc5-0ubuntu1) xenial; urgency=medium
* New usptream release (2.0.0~rc5)
- Fix a number of cgfs issues (LP: #1549363, LP: #1543697, LP: #1552355)
- Fix attach failing to allocate a tty (LP: #1551960)
This bug was fixed in the package lxc - 2.0.0~rc5-0ubuntu1
---
lxc (2.0.0~rc5-0ubuntu1) xenial; urgency=medium
* New usptream release (2.0.0~rc5)
- Fix a number of cgfs issues (LP: #1549363, LP: #1543697, LP: #1552355)
- Fix attach failing to allocate a tty (LP: #1551960)
A fix for this has been sent upstream. A new rc will be released very
soon with the fix.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
A fix for this has been sent upstream. A new rc will be released very
soon with the fix.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tried this again and the error is different now. I've attached a
debug log.
** Attachment added: "start_test.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+attachment/4587021/+files/start_test.out
--
You received this bug notification because you are a member of
I have tried this again and the error is different now. I've attached a
debug log.
** Attachment added: "start_test.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+attachment/4587021/+files/start_test.out
--
You received this bug notification because you are a member of
** Description changed:
I have a host where I create a privileged Xenial container. Inside that
privileged container, I create an unprivileged Xenial container using
the ubuntu user in the privileged container. When I try starting the
unprivileged container, I get the following error:
** Description changed:
I have a host where I create a privileged Xenial container. Inside that
privileged container, I create an unprivileged Xenial container using
the ubuntu user in the privileged container. When I try starting the
unprivileged container, I get the following error:
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543697
Title:
Unprivileged
32 matches
Mail list logo
