Search results

  1. F

    Container wont start

    root@proxmox:~# lxc-start -o lxc-start.log -lDEBUG -F -n 300 lxc-start: 300: conf.c: run_buffer: 353 Script exited with status 2 lxc-start: 300: start.c: lxc_init: 828 Failed to run lxc.hook.pre-start for container "300" lxc-start: 300: start.c: __lxc_start: 1914 Failed to initialize container...
  2. F

    Container wont start

    Yes i'm sure. root@proxmox:~# cat /var/lib/lxc/300/config lxc.arch = amd64 lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.monitor.unshare = 1 lxc.tty.max = 2 lxc.environment = TERM=linux lxc.uts.name = FHEM-Main lxc.cgroup.memory.limit_in_bytes = 4294967296...
  3. F

    Container wont start

    root@proxmox:~# lxc-start -n 300 -F root@proxmox:~# i did not get any info and no entry in task history.
  4. F

    Container wont start

    Hello! My containers wont start anymore. Job for pve-container@300.service failed because the control process exited with error code. See "systemctl status pve-container@300.service" and "journalctl -xe" for details. TASK ERROR: command 'systemctl start pve-container@300' failed: exit code 1...

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!