unable to stop unprivileged container using lxc-stop [ ubuntu 16.04 LTS, lxc version 2.0.8 ]
up vote
0
down vote
favorite
unable to stop the unprivileged container on ubuntu 16.04 LTS host with lxc-stop version 2.0.8 or 3.0.2. It hangs indefinitely.
Also, there is no IP associated with the container when using lxc-ls or lxc-info.
What I am missing in the configuration ?
Given below are some detail of the container q1.
config file:
Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = linux64
Container specific configuration
lxc.id_map = u 0 231072 65536
lxc.id_map = g 0 231072 65536
lxc.rootfs = /home/qbuser1/lxc/q1/rootfs
lxc.rootfs.backend = dir
lxc.utsname = q1
Network configuration
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:6a:8d:39
===========
qbuser1@ip-172-31-15-48:~$ lxc-info -P ~qbuser1/lxc -n q1
Name: q1
State: RUNNING
PID: 27356
Memory use: 4.90 MiB
KMem use: 0 bytes
Link: vethFMDWP4
TX bytes: 648 bytes
RX bytes: 798 bytes
Total bytes: 1.41 KiB
qbuser1@ip-172-31-15-48:~$ lxc-ls -P ~qbuser1/lxc --fancy
NAME STATE AUTOSTART GROUPS IPV4 IPV6
q1 RUNNING 0 - - -
qbuser1@ip-172-31-15-48:~$
ubuntu lxc containers
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
unable to stop the unprivileged container on ubuntu 16.04 LTS host with lxc-stop version 2.0.8 or 3.0.2. It hangs indefinitely.
Also, there is no IP associated with the container when using lxc-ls or lxc-info.
What I am missing in the configuration ?
Given below are some detail of the container q1.
config file:
Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = linux64
Container specific configuration
lxc.id_map = u 0 231072 65536
lxc.id_map = g 0 231072 65536
lxc.rootfs = /home/qbuser1/lxc/q1/rootfs
lxc.rootfs.backend = dir
lxc.utsname = q1
Network configuration
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:6a:8d:39
===========
qbuser1@ip-172-31-15-48:~$ lxc-info -P ~qbuser1/lxc -n q1
Name: q1
State: RUNNING
PID: 27356
Memory use: 4.90 MiB
KMem use: 0 bytes
Link: vethFMDWP4
TX bytes: 648 bytes
RX bytes: 798 bytes
Total bytes: 1.41 KiB
qbuser1@ip-172-31-15-48:~$ lxc-ls -P ~qbuser1/lxc --fancy
NAME STATE AUTOSTART GROUPS IPV4 IPV6
q1 RUNNING 0 - - -
qbuser1@ip-172-31-15-48:~$
ubuntu lxc containers
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
unable to stop the unprivileged container on ubuntu 16.04 LTS host with lxc-stop version 2.0.8 or 3.0.2. It hangs indefinitely.
Also, there is no IP associated with the container when using lxc-ls or lxc-info.
What I am missing in the configuration ?
Given below are some detail of the container q1.
config file:
Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = linux64
Container specific configuration
lxc.id_map = u 0 231072 65536
lxc.id_map = g 0 231072 65536
lxc.rootfs = /home/qbuser1/lxc/q1/rootfs
lxc.rootfs.backend = dir
lxc.utsname = q1
Network configuration
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:6a:8d:39
===========
qbuser1@ip-172-31-15-48:~$ lxc-info -P ~qbuser1/lxc -n q1
Name: q1
State: RUNNING
PID: 27356
Memory use: 4.90 MiB
KMem use: 0 bytes
Link: vethFMDWP4
TX bytes: 648 bytes
RX bytes: 798 bytes
Total bytes: 1.41 KiB
qbuser1@ip-172-31-15-48:~$ lxc-ls -P ~qbuser1/lxc --fancy
NAME STATE AUTOSTART GROUPS IPV4 IPV6
q1 RUNNING 0 - - -
qbuser1@ip-172-31-15-48:~$
ubuntu lxc containers
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
unable to stop the unprivileged container on ubuntu 16.04 LTS host with lxc-stop version 2.0.8 or 3.0.2. It hangs indefinitely.
Also, there is no IP associated with the container when using lxc-ls or lxc-info.
What I am missing in the configuration ?
Given below are some detail of the container q1.
config file:
Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.arch = linux64
Container specific configuration
lxc.id_map = u 0 231072 65536
lxc.id_map = g 0 231072 65536
lxc.rootfs = /home/qbuser1/lxc/q1/rootfs
lxc.rootfs.backend = dir
lxc.utsname = q1
Network configuration
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:6a:8d:39
===========
qbuser1@ip-172-31-15-48:~$ lxc-info -P ~qbuser1/lxc -n q1
Name: q1
State: RUNNING
PID: 27356
Memory use: 4.90 MiB
KMem use: 0 bytes
Link: vethFMDWP4
TX bytes: 648 bytes
RX bytes: 798 bytes
Total bytes: 1.41 KiB
qbuser1@ip-172-31-15-48:~$ lxc-ls -P ~qbuser1/lxc --fancy
NAME STATE AUTOSTART GROUPS IPV4 IPV6
q1 RUNNING 0 - - -
qbuser1@ip-172-31-15-48:~$
ubuntu lxc containers
ubuntu lxc containers
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
edited Nov 15 at 9:43
Rui F Ribeiro
38.2k1475123
38.2k1475123
asked Nov 15 at 2:49
Shyam
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 15 at 2:49
Shyam
1
asked Nov 15 at 2:49
Shyam
1
1
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Shyam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago
add a comment |
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Shyam is a new contributor. Be nice, and check out our Code of Conduct.
Shyam is a new contributor. Be nice, and check out our Code of Conduct.
Shyam is a new contributor. Be nice, and check out our Code of Conduct.
Shyam is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481830%2funable-to-stop-unprivileged-container-using-lxc-stop-ubuntu-16-04-lts-lxc-ver%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
can you attach to the container and get a list of processes running? that may help. Also pastebin any relevant logs you can gather.
– CameronNemo
2 days ago