d0us

Thanks for looking!

Thanks again for looking into this. I have fix common problems plugin? Could that have caused permission changes? Looks like I'm out of luck then? I haven't logged into the urnaid for a couple of months and don't know what has changed since . Guess I'll nuke it and start again :(. Thanks :)

This is the full error: root@me:~# lxc-start -F AMPDorothyLXC lxc-start: AMPDorothyLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 7) lxc-start: AMPDorothyLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "AMPDorothyLXC" lxc-start: AMPDorothyLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: AMPDorothyLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options I added this to enable tailscale from withing the lxc. I created another lxc and it starts so I think permissions are correct? When I look at the log as suggested by the prompt the error I see is this: Permission denied - Failed to exec "/sbin/init"

Hi thanks for your qucik reply, I think the broken config is for another lxc for obs which I messed up :D. The AMP one should be the standard template . Sorry I should have deleted that LXC before I created the diognostic dump. This is the error I get with the AMP lxc lxc-start: AMPDorothyLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 7) This is my AMP template (just redacted uniqe names etc): # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: --dist debian --release bookworm --arch amd64 # Template script checksum (SHA-1): 4a95b61004607fd2e89689cb76b94abf6da133d0 # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = linux64 # Container specific configuration lxc.rootfs.path = dir:/mnt/containers/lxc/<redacted>/rootfs lxc.uts.name = <redacted-hostname> # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.name = eth0 lxc.net.0.hwaddr = XX:XX:XX:XX:XX:XX lxc.start.auto = 0 # Allow TUN access lxc.cgroup2.devices.allow = c 10:200 rwm lxc.mount.entry = /dev/net/tun dev/net/tun none bind,create=file #container_description=Game Servers #container_webui=http://[IP]:8080 #container_supportlink=https://support.me.pls #container_donatelink=https://payme.now/pls

Hi, It's been a while since I started my AMP LXC which worked fine last time I span it up. But Now I get a cannot start error. I have incluced by diagnostic. Thanks :) dous-diagnostics-20250813-2257.zip

Thanks for the explanation, this makes sense :). I guess now that it runs fine in a VM with little fuss I'll keep it as it is, now that I know what the issue is. Thanks again

Hi all, This is probably the wrong place for this but I thought I'd post here just in case anyone here has experience of running AMP servers with the LXC plugin. I was hoping to move my Arma server from proxmox to Unraid using the LXC container. I installed AMP on a clean debian lxc as well as the AMP template with the same results: Arma encounters a segfault when starting. I don't get the same errors on Proxmox LXC or on a Debian VM on Unraid. When I searched for the error on the AMP discord it was interesting that any report of segfaults with Arma was "you're running it on Unraid". I thought running the AMP docker causes problems , but apparently even LXCs on Unraid apparently are not immune. So when it comes to running AMP, are the problems running dockerised AMP the same as using LXC on Unraid?