Recent content by mihalski

In fact the Ubuntu VM is inaccessible now.. It's running but seems to be totally unavailable. So.. I don't know what to do now..

So.. Debian with Docker doesn't work.. Ubuntu with Docker doesn't work either as can be seen below: [ 204.028007] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:35] [ 204.028007] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink...

Is there a Proxmox recommended Docker host OS? I'm currently using Debian 9.

How about these messages in the PVE system logs? Could these indicate something is amiss? [ 169.342702] kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable [ 272.283679] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750...

This problem only exists inside the VM, so that is why I am here trying to find out if there are some extra options I should be using when running docker inside a VM. I've found mention on the web that nested virtualisation (though I don't know if docker qualifies) requires additional settings...

I've been running Docker in a VM for a couple of months and recently upgraded from 4.4 to 5.0 (new install as my upgrade screwed up). I've created a new docker inside a VM and over the last 2 days as I've been expanding the configuration of my home automation docker running Home Assistant I've...

I've suffered through a lot.. but I've managed to recover my data and back it up.. now I want to clear out the space used by the old vm and can't: root@pve:~# lvremove /dev/pve/vm-102-state-WIP Do you really want to remove and DISCARD logical volume pve/vm-102-state-WIP? [y/n]: y Thin...

So is all hope lost now? root@pve:~# qm stop 102 VM still running - terminating now with SIGTERM VM still running - terminating now with SIGKILL root@pve:~# qm start 102 start failed: org.freedesktop.systemd1.UnitExists: Unit 102.scope already exists. root@pve:~# lvs LV VG Attr...

I have a sinking feeling that the Proxmox web UI let me obliterate my system without so much as a prompt :/ Unless the high CPU usage will lead to a working system.. I deleted the snapshot leaving only NOW for the docker. I can't even get a directory listing in the docker vm now.

1. What can I do about that without wiping necessary data (ie backups/snapshots seem like they could be deleted?) 2. Why does the system allow absolute failure like this if you run out of space? Is there a way to prevent this? On a non-virtual system things work to some extent, just with a bunch...

lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-aotzD- 51.41g 100.00 52.93 root pve -wi-ao---- 23.00g snap_vm-102-disk-1_WIP pve Vri---tz-k 32.00g data...

So I'm thinking.. Maybe? Possibly? I've run out of space in the VM storage? How could I check that? or fix it? Don't see how I could have used that much space but it's not impossible.

I only have one VM containing all my other containers using docker.. So this is quite a blow. If I run qm status 102 I get: status: io-error Not sure where to go from there in terms of debugging. Config is: qm config 102 balloon: 512 bootdisk: scsi0 cores: 2 description: Debian Stretch Linux...