ohai.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A cozy, fast and secure Mastodon server where everyone is welcome. Run by the folks at ohai.is.

Administered by:

Server stats:

1.8K
active users

#proxmox

48 posts44 participants7 posts today

New blogpost: "Trialling a move from a NUC to a container"

I spent some time today setting up a container to run my webserver and related tools (including mkdocs and hugo), as a test replacement for the current Intel NUC.

A current unknown - nothing like testing in production :) - is how well this small container will stand up to a lot of fedi-originated traffic. This is that test.

neilzone.co.uk/2025/04/trialli

Photo of me, a white man with a short dark beard, and dark hair, smiling at the camera, while sitting in front of a vintage terminal with green text on the screen.
neilzone.co.ukTrialling a move from a NUC to a container
More from Neil Brown
#FOSS#Linux#proxmox
Continued thread

Lastly, I have #immich in a #proxmox VM as a readonly viewer of the samba share so I can see photos on my phone and other devices. My devices connect to #wireguard when out of the house so they can still access the server to sync!

Hope that is helpful to someone, and let me know what I'm doing wrong and can improve!

🧵 4/4

Continued thread

Next I run #syncthing on my laptop, and on my #homelab #intelN100 #n100 mini pc / server that runs in the cupboard and is very #lowpower I run #proxmox and this also has a #samba share which allows any other network devices to see the media.

With syncthing running, I always have two copies of the media, but for backup I was using #rclone to send an encrypted copy to #googledrive - which I am in the process of switching over to #nextcloud running on #hetzner

🧵 3/4

Been testing out the #virtiofs support now baked into #proxmoxVE. It works, had to do some #selinux adjustments on #fedora to allow my #podman containers to use the mountpoint. Added this policy

```
(allow container_t unlabeled_t ( dir ( read write )))
```

In raw speed it is definitely not a winner - #nfs is easily double the speed. But on this particular VM I don't need the speed - it is nice that this is all self-contained now, and I can actually remove NFS altogether.

Seems like Snowflake proxy v2.11.0 uses more RAM, about 100 - 200 MB. This used to be around 20 - 50 MB.

Still have enough RAM on my Proxmox server to dedicate for this VM though so I now dedicate from 3 GB to 4 GB RAM since I run 20 snowflake proxy process on this VM.

I'm gonna check back later and see if it uses up all that 4 GB.

I use Fedora, btw.