May 03 04:14:34 keksmoks systemd: Killing process 2455 (lxc-start) with signal SIGKILL. May 03 04:14:34 keksmoks systemd: Control process exited, code=exited, status=1/FAILURE May 03 04:14:34 keksmoks lxc-start: lxc-start: 110: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the -logfile and -logpriority o May 03 04:14:34 keksmoks lxc-start: lxc-start: 110: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode May 03 04:14:34 keksmoks lxc-start: lxc-start: 110: tools/lxc_start.c: main: 329 The container failed to start May 03 04:14:34 keksmoks lxc-start: lxc-start: 110: lxccontainer.c: wait_on_daemonized_start: 874 Received container state "ABORTING" instead of "RUNNING" May 03 04:14:33 keksmoks systemd: Starting PVE LXC Container: 110.
Process: 2444 ExecStart=/usr/bin/lxc-start -n 110 (code=exited, status=1/FAILURE) Loaded: loaded static vendor preset: enabled)Īctive: failed (Result: exit-code) since Sun 04:14:34 CEST 15s ago See "systemctl status and "journalctl -xe" for details.Ĭommand 'systemctl start failed: exit code systemctl status - PVE LXC Container: 110 Job for failed because the control process exited with error code. Unfortunately I doesn’t work in my case pct start 110 # Drop TCP SYN,!ACK packets (new connections) not explicitly whitelisted aboveīreak # break can be overridden by a capabilityĬhr tcp_syn # TCP SYN (TCP flags will never match non-TCP packets) Or dport 5986 # PowerShell Remoting HTTPS # Allow the following TCP ports by allowing all TCP packets (including SYN/!ACK) to these ports # or not chr ipauth # OR IP addresses are not authenticated (1.2.0+ only!) If you want, you can config zerotier flow rules with some restrictions: # Whitelist only IPv4 (/ARP) and IPv6 traffic and allow only ZeroTier-assigned IP addressesĭrop # drop cannot be overridden by capabilities I haven’t tried setting up ZeroTier in a container but I have set it up on a VM and it works great.
0 kommentar(er)
