mlfh

The rclone fuse mount is essentially running in the memory of the container, and doesn't translate back into the filesystem that the host presents from itself into that container.

Since rclone is available in the debian repos, the simplest and easiest option would be to do the rclone mount on the host and then pass that via bind mounting into the Plex container.

If you want to keep the rclone mounting containerized though (or if your Proxmox host is clustered, you want to mount it on the host, and you want the mount to be shared between your nodes), you can use rclone's experimental but built-in nfs server feature: https://rclone.org/commands/rclone_serve_nfs/

Make sure your 2 containers can talk to each other over a secure network ("this server does not implement any authentication so any client will be able to access the data"), start the nfs server in the rclone container, and mount it via nfs in the Plex container.

Good luck!

Does the lion get prep time?

apt-get clean will clear the apt cache and should give you enough temporary storage headroom on /var to do things, but if you're bumping up on this limit often, you'll need to reconfigure your storage.

/var is often where processes dump a lot of data (logs, databases, etc), and subpartitioning of /var sets a cap so that when too much data is dumped there, the application crashes instead of the whole system. /var/log is often recommended to be subpartitioned separately as well, so that logging can still go on if the application data fills up and crashes.

These kinds of overruns can be intentional DOS attacks, also, so the subpartitioning is often a security recommendation. NIST 800-171 requires separate partitions for /var, /var/log, /var/log/audit, and /var/tmp

99 Luftballons is upbeat and fun, and about some balloons inadvertently kicking off a cataclysmic war that leaves the world in ruins.

I run a 3-node HA cluster. The extra functionality is really nice - live migrations are amazing, and the ability to move guests around gives you a lot of flexibilty.

If your third box supports it, I'd recommend installing proxmox pve alongside pbs on it (pve and pbs can run on the same node), and then create a cluster out of all 3. You don't even have to run any guests on that machine, if you want, but having the flexibility to is nice, along with having everything unified into one cluster.

Forgejo (Gitea fork used by codeberg.org) is a lightweight self-hostable option, and has a web-ui-based file editor. It's got an official docker image, and it's packaged for freebsd, as well, which makes it very easy to deploy and maintain either containerized or on a server.

With the size of modern linux kernels, I think 1GiB for a /boot partition is the absolute minimum I would go for a current full-sized distributuon. You'll run into these out-of-space issues on updates all the time otherwise.

I've used an old, out-of-support phone as a permanently plugged-in homeassistant control panel. Not quite self-hosting as in phone-server, but a fun easy project and a great way to keep an old device in use.

The bang syntax makes duckduckgo easily the best search engine - it's a shortcut to everything, the perfect gateway to the internet.

Can you give us the full output of the following commands?

ip addr

sysctl net.ipv6.conf.all.disable_ipv6

I have a playlist of the allegro movements from a bunch of baroque violin and harpsichord corcertos that is really nice to do intense head-down work to. Mostly Bach.
Baroque for the structure - feels mathematical and easy to predict and follow, making it easy to listen to while focusing on something else. The allegro movements for the pace - upbeat and invigorating. And a concerto has a great balance between large-scale blended orchestral sound and the melody of a lead instrument which also lends itself to supporting your focus on something else from the background.