Safe_mount: Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc"

1

Hi, there.

I’m deeply confused by this failure

root@pve:~# pct start 200
safe_mount: 1425 Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc"
lxc_mount_auto_mounts: 614 Operation not permitted - Failed to mount "proc" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" with flags 14
lxc_setup: 3906 Failed to setup first automatic mounts
do_start: 1273 Failed to setup container "200"
sync_wait: 34 An error occurred in another process (expected sequence number 3)
__lxc_start: 2114 Failed to spawn container "200"
startup for container '200' failed

Can anyone point out the central issue? (I’m tried many many methods that all fails to overcome the problem). It’s in a pve system (I’m not familiar with these subjects. But I just hope to resolve the issue so I can ssh to my personal account from the VSCode in my laptop.)

If you need further details, please let me know.
Thanks.

2

Well there’s very little info in your console logs I’m afraid, and it may be PVE-related. Maybe Proxmox’ forums would be better suited for your issue?

1 Like
3

This may be related Operation not permitted Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" - #7 by teoli

4

Thanks.

I was using a linux server using the ssh by VSCode installed on my (Windows) laptop. I used to connect to my personal account at the linux server. That worked well for several months.

This morning suddenly I find that I fail to connect to my server. And it appears that when I do pct list, the all items are “stopped”. Theoretically they could be started. But when I try to start the related port, it fails as shown.

I tried really many methods, virtually all, including that historical post. But it’s like finding a needle in an ocean—which is hopeless.

I guess it’ssafe_mount: not permitted - Fail to... that matters.

I’ll consider the Proxmox’s forum.

5

I think this thread is highly related (virtually the same) to my case.

LXC Containers won’t start after reboot | Proxmox Support Forum

I’ll try to see if I can understand what they are talking about. But I still hope anyone can teach me a simple and direct method to fix it. (It appears that a simple solution was not directly mentioned therein.)

6

@bensmrs Thank you so much. I’ve fixed the issue. I write my experience as follows.

Suppose I want to do pct start 50300.

Now I need to type zfs list and grab the name rpool/data/subvol-50300-disk-0.

Then I need to do zfs set atime=on rpool/data/subvol-50300-disk-0.

Then I need to modify, i.e. nano /etc/pve/lxc/50300.conf, and modify the status so that unprivileged: 0 be there.

For a feedback of a successful setting, type pct config 50300 | grep unprivileged and now we should see unprivileged: 0.

Now doing pct start 50300 should succeed.

7

Despite the success of pct start ...'s execution, my linux server now run into a worse condition: when I tried to ssh to the linux server from the VSCode of my laptop, the linux machine ran into a totally unresponsive state—it even fails to respond to a long press on the power button. And there is no more monitor output that can be seen.