I'm fixing the ordering now. Regarding the last part "This is still not
easy at all.": Do you mean that the message should be simpler (e.g.
Created adt-wily_1WtXPo)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Martin, can you please try with a fresh build from current lxc master
and report if the error still persists?
--
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/1551960
Title:
lxc-attach
Nevermind. You have the newest version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
To manage notifications about this bug
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** 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.
https://bugs.launchpad.net/bugs/1551935
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** 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.
https://bugs.launchpad.net/bugs/1551935
Title:
Fix present as pr on github against lxc master. Should be committed
soon.
** 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/1551960
Title:
Fix present as pr on github against lxc master. Should be committed
soon.
** 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.
** 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.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
To
** 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.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input
I'm fixing the ordering now. Regarding the last part "This is still not
easy at all.": Do you mean that the message should be simpler (e.g.
Created adt-wily_1WtXPo)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Martin, can you please try with a fresh build from current lxc master
and report if the error still persists?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work
Nevermind. You have the newest version.
--
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/1551960
Title:
lxc-attach does not work any more with input redirection
To manage notifications
** 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.
https://bugs.launchpad.net/bugs/1567037
Title:
lxc-attach crashed with SIGSEGV in get_pty_on_host()
To manage
Hi,
could you please attach the contents of the file
/var/log/lxc/(container).log as Serge suggested. That would be great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567037
Title:
lxc-attach
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1553097
Title:
lxc-attach does not output stderr any more if
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553097
Title:
lxc-attach does not output stderr any more if stdout is
Fix proposed (https://github.com/lxc/lxc/pull/873). Tests are included
as well.
--
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/1553097
Title:
lxc-attach does not output stderr any more
Fix proposed (https://github.com/lxc/lxc/pull/873). Tests are included
as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553097
Title:
lxc-attach does not output stderr any more if stdout is
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
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/1553097
Title:
lxc-attach does not output stderr any more if stdout
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553097
Title:
lxc-attach does not output stderr any more if stdout is redirected
I've reproduced this on a fresh standard xenial instance with LXD
2.0.8 and also on a xenial instance with a patched glibc that reports
ENODEV on ttyname{_r}() on a pty fd that does not exist:
root@x:~# ./enodev_on_pty_in_different_namespace
ttyname(): The pty device might exist in a different
On Tue, Jan 31, 2017 at 11:34:43AM +0100, Christian Brauner wrote:
> I've reproduced this on a fresh standard xenial instance with LXD
> 2.0.8 and also on a xenial instance with a patched glibc that reports
> ENODEV on ttyname{_r}() on a pty fd that does not exist:
&g
Public bug reported:
tcpdump segfaults when run in a LXD apparmor confined container:
driver: lxc
driverversion: 2.0.0
kernel: Linux
kernelarchitecture: x86_64
kernelversion: 4.9.0-3-generic
server: lxd
serverpid: 13543
serverversion: "2.8"
storage: zfs
storageversion: "5"
Hi, this is not a bug. What you want is to recursively bind-mount:
lxc.mount.entry = /home home none rbind,create=dir 0 0
Christian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657437
Title:
Well, the thing is that with the CVE patch applied, all kinds of things
won't work running Docker in an unprivileged container. So even if we
worked around the getPipeFds() issue, we'd still fail e.g. at setting
oom-score adjust because it also tries to access files under
/proc/. I think we will
Right, afaict this is caused by
https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378
. Marking the process as undumpable requires that the caller has
CAP_SYS_PTRACE in the target process user namespace. If not, then any
file-opening operations on /proc// (e.g.
Oh, that seems to be the fix for the CVE I made Aleksa Sarai aware of
that Roman Fiedler discovered (http://www.openwall.com/lists/oss-
security/2016/11/23/6,
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639345). I didn't
know that it was filed.
Anyway, I'll take a look.
--
You received
There is an upstream kernel fix for this:
https://lists.linuxfoundation.org/pipermail/containers/2017-January/037759.html
Until this is merged and then backported, I appended a workaround
whereby runC's init process will only set itself undumpable when it is
not running in a user namespace.
**
Note, that since a while LXC is sending SIGRTMIN+3 to systemd. So unless
systemd has changed it's shutdown/halt signal again LXC should send the
right signal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
criu crashes when a socket is located on a btrfs volume. We've hit this
bug during LXC live migration. It doesn't seem to be fixed with current
git head. This is reliably reproducible by just calling criu check.
However, the live migration code does not seem to call criu
Seem like a temporary failure when trying to import the `GPG` key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625078
Title:
lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12
To manage
Fix commited here:
https://github.com/lxc/lxc/commit/bfbf793616ce36ec63bac2cf582474c14cecb712
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix suggested https://github.com/lxc/lxc/pull/1282.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623143
Title:
Linux container does not take same cpu configuration as kernet's hosts
To manage
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271455
Title:
lxc-create does not honor $HTTP_PROXY when using a cached base image
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
Bugs, which is subscribed to Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543016
Title:
lxc-destroy --quiet is not quiet
To manage notifications about
I don't think we can change this behavior since too many users might
rely on this.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed by https://github.com/lxc/lxc/pull/760.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532125
Title:
lxc-clone: Use btrfs
LXC 1.1.* is deprecated and so is lxc-clone. Please switch to a newer
LXC version and use lxc-copy. Thanks!
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
LXC 1.1.* is deprecated so marking this as wont fix. Please update to a
newer version of LXC. Also, it seems that Serge's and Stéphane's
comments make this a valid candidate for invalid.
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because
The bug seems invalid. Furthermore, LXC 1.1.* is deprecated. Please
update to a recent version.
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See https://github.com/lxc/lxc/pull/1233.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591513
Title:
lxc-copy: bdev/bdev.c:
Marking as won't fix since LXC 1.1.* is EOL. Also, there have been quite
some improvements in btrfs handling on LXC side. If the issue still
persists, please feel free to report a bug against or repo on github.
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574969
Title:
Regression: "lxc-create -B best" stopped working
To manage
lxc-start-ephemeral is deprecated. Please switch to lxc-copy which
should support this.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix is available here: https://github.com/lxc/lxc/pull/1234.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302053
Title:
lxc-start
Patch provided by cypressyew upstream:
https://github.com/lxc/lxc/pull/1244.
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591513
Title:
lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522026
Title:
armhf lxd container does not start on arm64 system
To manage
lxc-execute now works correctly without a rootfs in LXC 2.*.*. So
closing this.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this still an issue? In any case, I think that this was caused by
trying to download an image that doesn't exist, e.g. a version of ubuntu
that we did not provide a ppc64el build at the time. We recently merge
https://github.com/lxc/lxc/pull/1232 which tries to be smarter about
downloading an
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623143
Title:
Linux container does not take same cpu configuration as kernet's
This sounds like a kernel bug to me. Can you please provide the output
of:
uname -a
and try to reproduce this on a newer kernel version and report back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This does not seem to be reproducible on a 4.4.0-45 kernel without
AppArmor stacking support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645037
Title:
apparmor_parser hangs indefinitely when
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624028
Title:
lxc create using debian template fails on ppc64el
To manage
On Thu, Dec 08, 2016 at 11:37:52AM -, John Johansen wrote:
> Christian,
>
> could you please try against my test kernel? It has fixed the issue with
> my local reproducer
Sure, I'm currently testing!
Thanks!
Christian
--
You received this bug notification because you are a member of
Fix suggested: https://github.com/lxc/lxd/pull/2693.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
** Changed in: lxd (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxd (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
** Changed in: lx
** Changed in: lxd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647639
Title:
lxc file push --recursive loses first letter of filename
To
On Thu, Dec 08, 2016 at 03:28:46PM +0100, Christian Brauner wrote:
> On Thu, Dec 08, 2016 at 11:37:52AM -, John Johansen wrote:
> > Christian,
> >
> > could you please try against my test kernel? It has fixed the issue with
> > my local reproducer
>
> Sure
Ok, I think I may have clue. You're using lxcfs in version 2.0.4. This
version of lxcfs does not handle uninitialized cpuset hierarchies
which can happen when systemd does not allocate a per-user cgroup in
the cpuset controller. I fixed this in lxcfs 2.0.5 by reimplementing
the cgroup handling
Please attach the container config file and show or attache the output
of the following commands:
- grep cgroup /proc/1/mountinfo
- cat /proc/self/cgroup
- ls -al /sys/fs/cgroup
- lxcfs --version
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Right, the cpuset bug is gone which was your main problem. Now the
only thing left to do should be:
chmod +x /home/sneetsher/.local
Please try again and report back. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Do you have libpam-cgfs installed? If not, could you install it,
reboot and report back if it works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649582
Title:
lxc-start fails to start a
Hi,
You can list the snapshots for a container by using:
lxc info trust1
Name: trust1
Remote: unix:/var/lib/lxd/unix.socket
Architecture: x86_64
Created: 2016/11/22 19:56 UTC
Status: Stopped
Type: persistent
Profiles: default
Snapshots:
zest1 (taken at 2016/11/22 20:57 UTC) (stateless)
Would
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623143
Title:
Linux container does not take same cpu configuration as
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649582
Title:
lxc-start fails to start a unprivileged container - cgroup
permissions
To
On Sat, Dec 03, 2016 at 12:58:54PM -, John Johansen wrote:
> How reliable/repeatable is this for you?
>
> I have been hammering a machine for multiple days and not been able to
> trip this once.
>
> I have been using the 4.8 ubuntu kernel the ubuntu-lxc/daily and the
> ubuntu-lxc/stable
lxc-create does not handle any web requests so this cannot be the cause.
Upgrading this to a secure connection is also perfectly fine. Is this
reliably reproducible still or was this maybe just a temporary server
problem?
--
You received this bug notification because you are a member of Ubuntu
** Changed in: lxc (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653725
Title:
lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
Hi,
Have you tried again after a while. I don't think that this is related to the
uid/gid mappings. In order for the download template to work you should have a
default lxc config for your unprivileged user configured which would list the
uid/gid mapping you want to use, e.g.
# Container
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653725
Title:
lxc-android-config not starting on ubuntu-touch/staging/*
Fix for screen merged upstream:
https://lists.gnu.org/archive/html/screen-devel/2017-03/msg00014.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in
** Changed in: screen (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
To manage
Can you please run LXD in debug mode
lxd --debug --group lxd
and then append the full log for one of the containers that fails to
start?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675760
Title:
@stgraber, that sounds like one of those empty directories similar to
the issues we had with the empty xen directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675760
Title:
rootfs issues -
Upstream screen patch:
https://lists.gnu.org/archive/html/screen-devel/2017-03/msg00013.html
** Changed in: screen (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So aside from the Ubuntu package being outdated (The codebase has indeed
changed massively.) the patch we need to get screen working properly is
way more intrusive then originally thought and there might even be the
case that we have to do some additional lower-level plumbing in the
kernel or
nt/4851595/+files/0001-screen-handle-pts-devices-in-different-namespaces.patch
** Changed in: screen (Ubuntu)
Status: Fix Released => In Progress
** Changed in: screen (Ubuntu)
Assignee: Stéphane Graber (stgraber) => Christian Brauner (cbrauner)
--
You received this bug notifica
Was this on a freshly created LXD instance or on an upgraded LXD
instance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675760
Title:
rootfs issues - 2.8 LXD release
To manage notifications
Pinged jjohansen to take a look whether he has seen this issue before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667444
Title:
Failed to start lxd container because it is already running a
I mean /var/log/lxd//lxc.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667444
Title:
Failed to start lxd container because it is already running a start
operation
To manage notifications
@fginther, it would be cool to see the dmesg output, /var/log/lxd,
/var/log/lxd//forkstart.log, /var/log/lxd/lxc.log. I
suspect, like Stéphane that this might be an AppArmor bug we've been
seeing quite regularly.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So this could be a potential kernel bug I'm not sure what LXD would do
that could cause this error. We should ping someone from the AppArmor
team and see if they have an ideas as to how this could be caused.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: tmux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
To manage notifications
About the tmux patch. Nicholas plans to merge a patch that is nearly
identical into tmux master sometime next week but this might be too late
for final freeze.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's a patch for the current tmux version of Ubuntu. We should get
this sorted before this Thursday.
** Patch added: "0001-handle-pty-devices-in-different-namespaces.patch"
I'll likely add another patch to this soon to handle some more corner-
cases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
To manage
I tested the screen-fifo-socket compatibility patch here
https://asciinema.org/a/111692 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
So, Stéphane brought to my attention that we're not including the patch
because it switches screen to use sockets instead of fifos and thus
makes it impossible to switch to existing fifo-based screen sessions.
I've written a patch that adds a compatibility layer to support both
fifo-based and
The screen patch is now also upstream
http://git.savannah.gnu.org/cgit/screen.git/commit/?id=565b8901cad828d921038cd6235501c42d1c9a32
. @stgraber, did you get around to pushing to to the archive as well so
that we can land this in zesty?
** Changed in: screen (Ubuntu)
Status: In Progress
This is expected. lxc-execute allows you to run commands without a
rootfs. Other isolation mechanisms are still available. Say, you have
sub{u,g}ids defined and you want to run a shell in a set of new
namespaces including user namespaces you can do:
sudo lxc-execute -n ns1 -l debug -o AAA -s
An upstream-compatible version of 0001-add-compat-layer-to-handle-both-
fifos-and-sockets.patch is now merged upstream into screen v4. See
https://lists.gnu.org/archive/html/screen-devel/2017-04/msg00023.html .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I sent a patch to musl upstream to align them with glibc. The patch is
merged: https://git.musl-
libc.org/cgit/musl/commit/?id=e1232f5b5185e8f337806841018369407e32e77d .
** Also affects: musl (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: musl (Ubuntu)
--
You
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's an updated version of the patch and a comment explaining in a
little more detail what is happening:
Subject: [PATCH] screen: handle pts devices in different namespaces
Various programs that deal with namespaces will use pty devices that exist in
another namespace. One obvious candiate are
** Changed in: tmux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: screen (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Since the Ubuntu screen package was synced with Debian yesterday the
attached patch does not apply cleanly anymore. So here's a new version
of it that also is much closer to what I've pushed upstream.
** Patch added: "0001-screen-handle-pts-devices-in-different-namespaces.patch"
The tmux patch is now also upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669578
Title:
Get ttyname() to work properly in containers
To manage notifications about this bug go to:
Updated version of fifo-socket-compat patch that removes left-behind
debugging statement.
** Patch added: "0001-add-compat-layer-to-handle-both-fifos-and-sockets.patch"
Hey everyone,
Uust as an fyi: I sent a branch https://github.com/lxc/lxc/pull/1713
which is now merged that makes LXC handle the hybrid cgroup case
provided the cgroup v2 mount does not bind any controllers (Which is the
current default). It will be included in the next LXC release.
Thanks!
1 - 100 of 355 matches
Mail list logo
