Search results

Did you check using the above path or simply /etc/lsb-release from inside the containers? The above path is where the file systems get mounted to during startup of the container, and the file is part of ubuntu's `base-files` package, so it would be rather unusual for it not to exist. Can you...

Some of that output looks truncated, so I'm not sure where the prestart hook actually fails. You could just try a `pct mount 300` to check if the mounting works at all (and `pct unmount 300` afterwards). Can you also post your /etc/pve/lxc/300.conf file?

You'll want to pass a few more parameters to lxc-start: # lxc-start -o lxc-start.log -lDEBUG -F -n 300 Then paste both the output you get as well as the contents of the `lxc-start.log` file created by the above command.

In the VM's Hardware tab, if you open the edit window for a network device, there's a Firewall checkbox you need to check. You'll then see iptables chains named `tap100i0-IN` or `veth321i2-OUT` along with additional firewall link/bridges.

To get the loop nodes: lxc.mount.entry = /dev/loop0 dev/loop0 none bind,create=file 0 0 lxc.mount.entry = /dev/loop1 dev/loop1 none bind,create=file 0 0 (...) lxc.mount.entry = /dev/loop-control dev/loop-control none bind,create=file 0 0 Please note that you should only do this in trusted...

For VMs only the VM level is relevant. And you need to make sure the firewall is enabled in all places David mentioned above.

You can try `lxc-usernsexec -m b:0:100000:65536 /bin/bash` after mounting, but then you'll effectively be user 100000 on the host, so you won't be able to copy files to your target unless you use some kind of authentication in between (eg. using rsync over ssh).

It's not. It would only be used if you remove the veth (or tap for VMs) device from the bridge, configure an IP address on that device directly and used that to communicate with the guest. veth or tap devices behave like virtual ethernet cards. What you see on the host is your host side of it...

Hängt vom umliegenden Netzwerksetup ab. Bei den meisten Hostern (netcup, OVH, Hetzner etc.) wird erwartet, dass die ganze IPv6 range auf der MAC addresse deines hosts liegt, da musst du IPv6 routen, und neighbor discovery proxy einrichten, da der äußere Gateway neighbor discovery auf der ganzen...

Depends on the setup. Generally, ZFS does a lot, so for a real comparison you'd need to put a file system onto the SW RAID block so that you end up with comparable features. It doesn't make much sense to compare an ext4 on SW-RAID1 to a ZFS mirror in my opinion. Also note that you can easily add...

That error usually happens when you try to use VLANs on a non-vlan-aware bridge without physical interfaces. Try enabling vlan filtering on the bridge.

@1 & 2 Features. And it's usually use-case dependent, so I'll leave these 2 to the community. @3 Not having a lot of RAM isn't really a *problem* in the sense that things would start breaking (unless you go RALLY low...). But you need a certain minimum amount for reasonable performance. I've...

Apart from what I wrote above (installing the kernel module on the host) there shouldn't be. You'll just need the wireguard userspace tools inside the container to configure the interfaces.

You can run `vma extract vma.dat SomeDirName` and see what comes out. There's a chance you'll get a disk image file `SomeDirName/tmp-disk-drive-scsi0.raw` for example, containing the equivalent of having filled the VM's drive with zeros starting at some random point in the middle wherever the...

There should be a fedora 28 template available now.

There should be one available soon. In the mean time you can use one from lxc's images server. Just fetch the rootfs.tar.xz and give it a recognizable name, and put it in your template storage's template/cache/ dir. [1] http://images.linuxcontainers.org/images/

Tried it here. To me this looks like a bug in their systemd version. Fedora 28 works again...

All our containers include /usr/share/lxc/config/common.conf which in turn includes all .conf files in /usr/share/lxc/config/common.conf.d/ - You can add eg. a file 99-pid-limit.conf to that directory and add the above cgroup line to it.

Also note the related entry here[1]. The default size is a guess made by the LVM tools, and was updated by us on our ISO after users started having issues with that. [1] https://bugzilla.proxmox.com/show_bug.cgi?id=1241

But there the disk had `backup=0` when the error was posted.