Container Creation Fails With Ubuntu Minimal (Core)


New Member
Jul 1, 2020
I'm trying to create a container based on the Ubuntu Minimal, available here. The disk seems to be created successfully, but then it fails on the network interface. I have tried both Bionic and Focal. Here is the output:

 Logical volume "vm-105-disk-0" created.
mke2fs 1.44.5 (15-Dec-2018)
Discarding device blocks:    4096/2097152               done                           
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 4983d47c-59f8-49ad-8cf8-4339583bb558
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables:  0/64     done                           
Writing inode tables:  0/64     done                           
Creating journal (16384 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information:  0/64     done

extracting archive '/var/lib/vz/template/cache/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz'
Total bytes read: 68843520 (66MiB, 164MiB/s)
Detected container architecture: amd64
unable to open file '/etc/systemd/network/' - No such file or directory
  Logical volume "vm-105-disk-0" successfully removed
TASK ERROR: unable to create CT 105 - error in setup task PVE::LXC::Setup::post_create_hook
Upon further consideration, I believe this is due to the root fs being read-only.


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 your own in 60 seconds.

Buy now!