lxc-console broken for systemd containers under hosts without systemd #1704
Comments
|
Did you recently upgrade your lxc version? |
|
I think it was the latest update that broke things. Centos / Ubuntu containers were working on May 1st - 3rd while I was using them to test some scripts
|
|
looking at the PR's the containers were working on 7th June too |
|
Can you show me the containers config file, please? |
|
__________________________________________________-
Alpine Linux containers on the same I use a |
|
Can you show what happens in the terminal when you do |
|
What os did you test in ? this is in Alpine Linux after hitting enter 5-6 times:
& this is Manjaro OpenRC after hitting enter 5-6 times:
|
|
& this is an Alpine Linux container starting as expected under Manjaro OpenRC:
|
|
Ok, can you ease start a container that has this problem with |
|
|
|
for comparison these are similar logs from an Alpine Linux container that starts ok: |
|
Cheers, not that I'm currently in the middle of a big chunk of work in LXD so this will have to sit for a bit. Sorry about that. I'll definitely come back to this! |
|
ok no problem |
|
Facing the same issue |
|
@itoffshore, @Chetan21, can you try and reproduce this behavior with |
|
NVM.. I could not reproduce. But, in general, there seems to be a lot of problems with CentOS LXC containers. Switched to debian containers, works well! |
|
Steps followed for that error, were exact as mentioned by @itoffshore in previous comments on updated |
|
@Chetan21, but you were unable to reproduce? |
|
I still have the same errors with |
|
Right, I think the explanation is rather simple. Can you show me the full process tree for one of those containers that don't allow for proper |
|
I'm able to |
|
That looks like you're not using Can you please also show:
from the host. |
|
|
|
For the systemd container the and start the systemd container again. |
|
Yes that fixed it - thanks ever so much for looking at this issue. Should this functionality be part of |
|
liblxc doesn't care what runs inside the container at all so it won't know whether it needs to create the cgroup in question or not. openrc will likely not want to have a |
algitbot
pushed a commit
to alpinelinux/aports
that referenced
this issue
Nov 26, 2017
* systemd based containers require the /sys/fs/cgroup/systemd cgroup for lxc-console and services inside the containers to work * systemd_ctr() based on recommendations from lxc: lxc/lxc#1704 (comment) Committer note: I did few minor modifications.
|
Having the same issue with systemd cgroup present |
|
The $PATH seams okay from the lxc-console |
|
Same "group error" output with the prebuilt Ubuntu image using the download template. Systemd started normally on the Ubuntu container and nothing seams broken but yet, interfacing with the containers from python seams fine. I cant figure out why the group ID 19 cannot be found or need |
|
What happens if you do sudo lxc-attach --clear-env -P /home/madara/containers -n ubuntu |
|
@brauner same "group error" |
|
The warning about the gid is not really an issue. I might send a small fix though once I've convinced myself that this is the right thing to do. :) |
brauner
pushed a commit
to brauner/lxc
that referenced
this issue
Apr 9, 2018
Closes lxc#1704. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
brauner
pushed a commit
that referenced
this issue
Apr 20, 2018
Closes #1704. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
Blub
pushed a commit
to Blub/lxc
that referenced
this issue
Jul 2, 2018
Closes lxc#1704. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
geaaru
pushed a commit
to geaaru/lxc
that referenced
this issue
Jul 4, 2018
Closes lxc#1704. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
ghost
mentioned this issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Distributions: Alpine Linux (OpenRC) / Manjaro (OpenRC) / Antix Linux (Sysvinit)
Distribution versions: Alpine 3.6 / Manjaro 17.0.2 / Antix 17-b1
lxc-start --version=2.0.8Issue description
lxccontainers under nonsystemdhosts were working until about 4 weeks ago. At the momentlxc-consoleconnects to attybut does not give a login prompt. Containers are started ok withlxc-startbut cannot be stopped withlxc-stop. Usinglxc-attachto connect to a container shows an error of:groups: cannot find name for group ID 19(this is theloggroup on thelxchost).Inside the container
$PATHdoes not seem to work (calling binaries stopped working) &openssh-serverhas stopped working in the containers. (I have been using ubuntu / centos containers created withlxc-create -t download).Steps to reproduce
lxc-create -t download -n <container>lxc-start -n <container>lxc-console -n <container>Information to attach
lxc-start -n <c> -l <log> -o DEBUG- this gives a337megcore dumplxc-start -n ubuntu2 -l trace -o ubuntu.lxc.log:The text was updated successfully, but these errors were encountered: