Search results

I did not reboot or any other. My error message was in the OP. No memory issues.

I only have 2 devices available, it's my personal test system. Cant add a 3rd node... Now, a day later it just seems to work... was there an issue with the online installers?

following: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 Is use: https://pve.proxmox.com/wiki/Package_Repositories Proxmox VE No-Subscription Repository apt dis-upgradefails: W: (pve-apt-hook) !! WARNING !! W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W...

So, some final help here. do I need to go from this: mount -vvv -t cifs -o username=frigate,password=nono,domain=WORKGROUP //192.168.1.100/frigate/clips /shared/frigate/clips mount -vvv -t cifs -o username=frigate,password=nono,domain=WORKGROUP //192.168.1.100/frigate/recordings...

Sorry, in your example: //192.168.1.100/frigate/clips /shared/frigate/clips /shared/frigate/clips cifs username=frigate,password=nono,domain=WORKGROUP 0 0 this: /shared/frigate/clips /shared/frigate/clips is in double. Is that an error?

Thank you, I had that before but I am struggling with the correct format I think. Is there double /shared/frigate/clips in your line? Why? I had before - but that was splitted later by 3 separate shares on advise of the frigate guys. //192.168.1.100/frigate/ /shared/frigate/ cifs...

Hi! I need some help to make these mounts reboot proof... what's the best way in my LXC2? mount -vvv -t cifs -o username=frigate,password=nono,domain=WORKGROUP //192.168.1.100/frigate/clips /shared/frigate/clips mount -vvv -t cifs -o username=frigate,password=nono,domain=WORKGROUP...

The entire NUC was replaced and problem solved.

Thank you for your time

Sorry, going round in circles here.... why would restore from backup start docker in my container? What is the rationale? What is the issue in here?

Now cant login to the LXC container anymore. starting up but nothig then....

I do not know for sure. I would NOT expect this to be changed do to an upgrade. Also, I cannot set it back. Also, since backup/restore seems to be the only way to set unprivileged back. (see post #7).

I hope on some explanation of "Proxmox Staff Member"

Shouldn't the tickbox "Unprivileged container" being "No" for running docker in LXC not be "Yes"?

Sorry, thisis going from worse to more worse. The LXC always worked. I have multiple of those with docker inside. Worked for years... now after updating proxmox to 7 it wont start dockers. How is reinstalling docker going to solve anything in a always working LXC container?

Why is my container not unpriviliged anymore after update to 7 (from 6)

root@frigatelxc ~# root@frigatelxc ~# journalctl -fu docker -- Logs begin at Tue 2022-03-15 18:55:39 CET. -- Mar 15 18:55:43 frigatelxc systemd[1]: docker.service: Failed with result 'exit-code'. Mar 15 18:55:43 frigatelxc systemd[1]: Failed to start Docker Application Container Engine. Mar 15...

LXC Containers starts (and started) correctly... root@frigatelxc ~# systemctl status docker.service * docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue...

Sorry, to be 100% sure... this file still is: /etc/pve/lxc/108.conf: arch: amd64 cores: 4 features: mount=cifs,nesting=1 hostname: frigatelxc memory: 8192 nameserver: 192.168.1.90 192.168.1.91 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=b2:72:05:93:9e:23,ip=dhcp,type=veth onboot: 1 ostype...

root@proxmox02:/tmp# nano lxc-108.log GNU nano 5.4 lxc-108.log * lxc-start 108 20220315175112.114 INFO seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for...