Search results

Thank you for such a thorough and thoughtful reply. I will digest in full and read the linked article. After a quick first glance, I suspect I'm heading for pbs installed on a vm inside my pve locally, and syncing to a remote pbs at the second residential location. Though I still have to...

I would like a backup solution that is proportionate to the requirements of a home lab: something that 'makes sense' in terms of backup security (e.g. backups should ultimately reside at a remote location), but where performance/availability etc are not critical considerations. Both my local...

Has anyone else got rootless podman working on Proxmox 8.2? I Still haven't been able to crack this. I did have a similar rootless podman running in an unprivileged container back in January but that was on an older Proxmox version and older ubuntu.

I have installed podman 4.3.9 on ubuntu 22.04 in an lxc that's running on Proxmox 8.2.7. When I run podman run --name basic_httpd -dt -p 8080:80/tcp docker.io/nginx The container produces the following error message: podman@pods:~$ podman run --name basic_httpd -dt -p 8080:80/tcp...

I've just tried this with podman 4.3.1 and it seems to be working in rootless. If you're going to do rootless podman, remember to edit ~/.config/containers/storage.conf rather than /etc/containers/storage.conf. And you might want to use the rootless_storage_path directive instead of graphroot...

I should add: The host: root@toast:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian And root@toast:~# pveversion pve-manager/8.1.3/b46aac3b42da5d15 (running kernel...

I'm trying to get fuse configured in a container but /dev/fuse is always owned by nobody:nogroup unless I chown the /dev/fuse on the proxmox host itself. I'd like user 10000 in the container to own /dev/fuse in the container. Container user 10000 is mapped to 110000 on the host. If I chown...

very timely info for me. Thank you. But possible typo in your storage.conf Should "/usr/local/bin/overzfsmount" be "/usr/local/bin/overlayzfsmount"?

Great! thank you.

Hi, I've got a legacy mount point in a container that is owned by nobody:nogroup and I can't rmdir it or chown it, even as root. Can anyone advise how I can remove this directory? This situation arose when I specified a bind mount in the lxc .conf file without first creating a mount point in...

Hi all, I'd like to start using acls on bind mounts in my Linux containers. My filesystem is ZFS. I've read that ZFS uses nfsv4 acl while linux uses posixacl which can cause some problems if incorrectly configured. Please could you advise the right approach. Wiki states "ZFS uses as default...

Hey. Been a while since I looked at this, but I think there might be some confusion arising from 'mapping'. IIRC the lines which you're referring to aren't mappings. They are ranges. So, in these cases, the 'root' user is allowed to impersonate a range of uids from 100000 up to 165536, and a...

Hmm. Getting very similar behaviour with a new CentOS 8 container. In the past I have created both CentOS 7 and CentOS 8 containers and haven't had network or dbus issues. Though I can't be sure of what version of Proxmox that was with - it was a few weeks back.

Hi, I'm having major network difficulties with a fresh container install of CentOS 7 using the standard template and would welcome any help to resolve it. I can connect via pct from the host, but I can't ping from the container, the response is: [root@test ~]# ping 8.8.8.8 connect: Network is...

Just a bit more info on this in case it highlights a problem in my configuration. I have set up an automatic zfs scrub with zfs-zed and succesfully get emails when it does its thing. So it's not email per se that's the problem. It's just that I'd also like to receive emails when Proxmox...

Hi, Is there a way to get Proxmox to send an email when it encounters an error? For example, one of my containers refused to start recently (it had run out of disk space). In the task list of the proxmox GUI, the task to start the container was highlighted in red and had an error description...

Great! Silly error on my part. Thanks very much for solving it.

Unfortunately it looks like the problem persists after apt full-upgrade and reboot of host. #pct start 115 run_buffer: 323 Script exited with status 1 lxc_init: 797 Failed to run lxc.hook.pre-start for container "115" __lxc_start: 1896 Failed to initialize container "115" startup for container...

Thanks for the fast response. The container used to boot at startup of the host. I've tried to start it from the GUI by selecting the container and clicking start at the top of the page. And I've tried pct start 115 from the command line of the host. I can't execute reboot at the moment...

Hi, One of my four containers refuses to restart after a recent power outage. I'd be grateful of steps I can take to try to resolve it. I've tried issuing the command: lxc-start -n 115 -F -lDEBUG -o temp/lxc-115-2.log: Here's the output at the command line lxc-start: 115: conf.c: run_buffer...