From: egrain <egrain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] users running unprivileged lxc container no worky no more.
Date: Mon, 15 Aug 2022 11:06:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38682@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2414 bytes --]
New issue by egrain on void-packages repository
https://github.com/void-linux/void-packages/issues/38682
Description:
### Is this a new report?
Yes
### System Info
5.18.17_1 #1 SMP PREEMPT_DYNAMIC Fri Aug 12 13:53:18 UTC 2022 x86_64 GNU/Linux musl.
### Package(s) Affected
lxc-5.0.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
It working like it did before the update. All I did was XBoxPlayStation-install -Su and init 6.
### Actual behaviour
lxc-start: alpina: ../src/lxc/network.c: lxc_create_network_unpriv_exec: 2990 lxc-user-nic failed to configure requested network: ../src/lxc/cmd/lxc_user_nic.c: 802: create_db_dir - Permission denied - Failed to create /run/lxc
../src/lxc/cmd/lxc_user_nic.c: 1125: main: Failed to create directory for db file
lxc-start: alpina: ../src/lxc/start.c: lxc_spawn: 1840 Failed to create the network
lxc-start: alpina: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "alpina"
lxc-start: alpina: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: alpina: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
and if i mkdir /run/lxc, chown lxcuser /run/lxc i get this:
lxc-start: alpina: ../src/lxc/network.c: lxc_create_network_unpriv_exec: 2990 lxc-user-nic failed to configure requested network: ../src/lxc/cmd/lxc_user_nic.c: 474: instantiate_veth - Operation not permitted - Failed to create veth1003_cv7j-veth1003_cv7jp
../src/lxc/cmd/lxc_user_nic.c: 529: create_nic: Error creating veth tunnel
../src/lxc/cmd/lxc_user_nic.c: 720: get_nic_if_avail: Failed to create new nic
../src/lxc/cmd/lxc_user_nic.c: 1206: main: Quota reached
lxc-start: alpina: ../src/lxc/start.c: lxc_spawn: 1840 Failed to create the network
lxc-start: alpina: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "alpina"
lxc-start: alpina: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: alpina: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
### Steps to reproduce
Have a working lxc user + container.
Update the system.
Reboot.
Try and start it with: lxc-start -n nameofyourcontainer -F
Thanks for reading.
next reply other threads:[~2022-08-15 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:06 egrain [this message]
2022-08-16 19:25 ` CameronNemo
2022-08-16 19:35 ` egrain
2022-08-16 20:15 ` CameronNemo
2022-08-16 20:15 ` CameronNemo
2022-08-16 20:16 ` CameronNemo
2022-08-16 20:20 ` CameronNemo
2022-08-16 20:27 ` egrain
2022-08-16 20:32 ` CameronNemo
2022-08-16 20:35 ` egrain
2022-08-16 20:38 ` CameronNemo
2022-08-16 20:39 ` egrain
2022-08-17 0:44 ` eli-schwartz
2022-08-17 2:56 ` eli-schwartz
2022-08-17 3:01 ` eli-schwartz
2022-08-17 8:29 ` egrain
2022-08-17 14:31 ` [ISSUE] [CLOSED] " paper42
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38682@inbox.vuxu.org \
--to=egrain@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).