Container Start Failed

Zeki Celikbas

New Member
Jan 2, 2019
5
1
3
55
Hi to all Community,

I'm using Proxmox Virtual Environment 5.1-40 Today I'm updated my proxmox OS (I've no subscription). After that I couldn't start my debian Containers. I've installed a fresh one but it doesn't start like old ones.

Here is my error codes:
On Web Interface:
TASK ERROR: command 'systemctl start pve-container@102' failed: exit code 1

On command line:
# lxc-ls -f
NAME STATE AUTOSTART GROUPS IPV4 IPV6
100 STOPPED 0 - - -
102 STOPPED 0 - - -
103 STOPPED 0 - - -
104 STOPPED 0 - - -
root@lightyear:~# lxc-start -n 100
lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
lxc-start: 100: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: 100: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
lxc-start: 100: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.

When I try this way I got the following error
# lxc-start -n 100 -F
lxc-start: 100: lxccontainer.c: do_lxcapi_start: 984 Permission denied - Failed to make / rslave at startup
 
Hi Again,

I think it's about permissions. But I couldn't find which permissions to which files/directories. Here is more detailed logs:

Code:
# lxc-start -n 102 -F -lDEBUG -o lxc-102.log --logpriority TRACE
lxc-start: 102: lxccontainer.c: do_lxcapi_start: 984 Permission denied - Failed to make / rslave at startup
lxc-start: 102: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: 102: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.

root@lightyear:/rpool/data# cat lxc-102.log
      lxc-start 102 20190102105205.656 INFO     lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/102/config
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:290 - command get_init_pid tries to connect command socket
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:295 - command get_init_pid failed to connect command socket: Connection refused
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:290 - command get_cgroup tries to connect command socket
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:295 - command get_cgroup failed to connect command socket: Connection refused
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:do_lxc_cmd_get_cgroup_path:439 - command get_cgroup failed for container "102": Connection refused.
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:290 - command get_state tries to connect command socket
      lxc-start 102 20190102105205.656 TRACE    lxc_commands - commands.c:lxc_cmd:295 - command get_state failed to connect command socket: Connection refused
      lxc-start 102 20190102105205.656 TRACE    lxc_start - start.c:lxc_init_handler:592 - unix domain socket 4 for command server is ready
      lxc-start 102 20190102105205.656 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
      lxc-start 102 20190102105205.656 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 102 20190102105205.656 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

I've found these lines in journalctl-xe command:

Code:
-- The start-up result is done.
Jan 02 13:52:05 lightyear audit[25194]: AVC apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=25194 comm="lxc-start" flags="rw, rslave"
Jan 02 13:52:05 lightyear kernel: audit: type=1400 audit(1546426325.656:21): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=25194 comm="lxc-start" flags="rw, rslave"
Jan 02 13:53:00 lightyear systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
 
Hi Oguz (Merhaba)

Yes for last e few minutes I'm working about apparmor. Here is my versions:
apparmor,2.11.0-3+deb9u2
libapparmor-perl,2.11.0-3+deb9u2
libapparmor1,2.11.0-3+deb9u2

I don't have any commercial support because of this I was thinking about to upgrade with pve-no-subscription repository. At the moment do you suggest to do this?

deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

Thanks (tesekkurler)

zeki
 
Thanks to all people helped me about to solve this problem. It was about the permissions and I think because of apparmor package. My problem solved after upgrade my system to Proxmox Virtual Environment 5.3. I think the problematic packages upgraded while this proggress.

Thanks Again.

Zeki
 
  • Like
Reactions: oguz
I don't have any commercial support because of this I was thinking about to upgrade with pve-no-subscription repository. At the moment do you suggest to do this?

I'm glad the problem is solved. The commercial support is not required for any functionality in the software, and it is always recommended to get the latest versions of packages from the repositories.

Just out of curiosity and information, what was the previous PVE version before the upgrade?
 
I'm glad the problem is solved. The commercial support is not required for any functionality in the software, and it is always recommended to get the latest versions of packages from the repositories.

I'm agree

Just out of curiosity and information, what was the previous PVE version before the upgrade?

it was proxmox-ve: 5.1-31
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!