Search results

Did you start it using sudo ?

Did not try the latest ISO, but apparently nothing changed in the installer, so it should still work. If not, just le know. More info in the repo or in this thread: https://forum.proxmox.com/threads/proxmox-installation-via-pxe-solution.8484/

Ah, during startup and package update, it seems to renew it's lease: Aug 02 09:11:31 dc3 dhcpd[25938]: DHCPACK on 10.0.0.137 to 1a:f5:05:56:50:c3 (ubuntu) via ens18 Aug 02 09:12:28 dc3 dhcpd[25938]: DHCPACK on 10.0.0.137 to 1a:f5:05:56:50:c3 (ubuntu-runner-2) via ens18 [code]

The wiki already mentions a problem with the cloud-init images default hostname, which should work with versions > 18.2. However, i tried latest bionic image with 18.2-27-g6ef92c98-0ubuntu1~18.04.1 and it still get's it's dhcp lease for ubuntu rather then the vm hostname (which is properly set...

Been using this since 2016 :) https://morph027.gitlab.io/post/zfs-docker/

You can have a look at this: https://git.proxmox.com/?p=pve-docs.git;a=blob;f=qm-cloud-init.adoc;h=cfac011c659440e4b4b91d985dea79f98e5f083c;hb=HEAD

Hmpf... ls -la /dev/zvol/rpool/data/vm-102-disk-1*

mount -o ro /dev/zvol/rpool/data/vm-102-disk-1-part2 /mnt/loop/

Hm ... looks like there is no partition yet. Is there an OS installed already?

Can you list the partitions with fdisk before?

You might need to address the proper partition (as it's a block device) ~# fdisk -l /dev/zvol/rpool/non-critical-vm/vm-159-disk-1 Disk /dev/zvol/rpool/non-critical-vm/vm-159-disk-1: 128 GiB, 137438953472 bytes, 268435456 sectors Units: sectors of 1 * 512 = 512 bytes Sector size...

Happy birthday and thank you!!!

https://github.com/dm-vdo/kvdo :) From what i see, basically the same like ZFS can do already (dedup, compression) but for LVM ... quite impressing.

Depends...i think it's 2 different tools for different use cases...i like to use both of them but mixing up might not be a good idea.

I really like Docker and I am a heavy user, but it does not quite compare to lxc to me. You run a single app inside a docker container, no init system, nothing else. With lxc, you get the whole OS stack and can run complex apps (classical LAMP,...) including config management, updates and so on...

Jip, same here. Probably because it's a beta kernel..

In fact, it is loading /boot/pve/vmlinuz with /boot/pve/initrd.img which is a symlink to the latest installed kernel. root@proxmox:~# cat /etc/systemd/system/kexec-pve.service [Unit] Description=boot into into the current pve kernel Documentation=man:kexec(8) DefaultDependencies=no...

Some of ours: root@itchy:~# zpool status rpool pool: rpool state: ONLINE scan: scrub repaired 0B in 0h13m with 0 errors on Sun Mar 11 00:37:30 2018 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0...

I could not get nginx working, so i'm using HAProxy: https://forum.proxmox.com/threads/pxve-nginx-websocket-proxy.20886/#post-139486

Can you try to add a trailing slash to the proxy_pass host? Without I guess nginx is passing /subdir to pve which will it work. Otherwise your rewrite rule needs to strip /subdir from the request.