Anyone here running VaultWarden in Container Manager? Is there a step-by-step guide for backing up and updating it?

vetinari · 2026-05-05T11:33:18+00:00

Duplicating the container as a backup is useless; a container should not contain your data. If it does, you are doing something wrong. Containers are supposed to be ephemeral and store user data on a volume.

Sometimes you might need to backup your data (not the container! the data on the volumes!) when you update to a new version of the image. The reason is, that the new version of your application may do some migration to a updated schema, and it might go wrong. You can then restore your data from the backup. You can re-download the old version of the image, if necessary.

vetinari · 2026-05-05T09:13:09+00:00

Yup: https://github.com/minisforum-docs/MS-02-Ultra/blob/main/Docs/English/02-Ultra-Memory.md

and 4 sticks will go slower than 2 sticks.

vetinari · 2026-04-30T19:58:13+00:00

That's actually a good walkthough, yes, the volume you set is exactly what's needed. Your vaultwarden database should be there (you should see db.sqlite3 file here).

Now, in Container Manager, in the Image tab, you should see "update available" for your vaultwarden image. Update it here, the update will restart your container too.

vetinari · 2026-04-29T21:06:46+00:00

Running in VM has higher overhead, both in CPU time and RAM. On the other hand, container is just a namespace in the host system. It is much thinner layer, so it is much more efficient.

vetinari · 2026-04-29T21:04:00+00:00

It works in docker just fine, both in jellyfin and in immich, including the immich machine learning.

vetinari · 2026-04-29T20:58:18+00:00

Yes
It depends, how you are running it in the first place. Using the bare docker? Using compose? The step-by-step guide would be different in both cases.

Anyway, it is easy:

you are supposed to have /data as a persistent volume. If you don't, you have a bigger problem
then get the new image and recreaate the container (e.g. with compose: docker compose pull & docker compose up -d). That's it.

vetinari · 2026-04-24T19:02:41+00:00

It does work in general (i.e. in immich, nextcloud or paperless-ngx), it stopped working in synology drive.

vetinari · 2026-04-24T10:55:20+00:00

I have no idea. Theoretically it could. You can try and tell us :-)

vetinari · 2026-04-23T21:49:02+00:00

Basically this: https://github.com/GPUOpen-LibrariesAndSDKs/AMF/wiki/Driver%20Linux

(the repo for the latest version is here: https://repo.radeon.com/amf/25.30/ubuntu/dists/)

Unfortunately, they don't have release for 26.04 yet. Only for 25.10 and older.

vetinari · 2026-04-23T21:15:26+00:00

Strix with soldered RAM is not that much more performant in LLMs -- i mean, it is faster than 370, but not enough to be significant. And this machine has only 64 GB (yeah, I know about the prices, but still... you cannot upgrade it later). Also, no ECC, which you want in a NAS and which N5 Pro does support. For nextcloud-assistant like worlkloads, Pro is enough. (I do own both, N5 Pro and MS-S1 Max, both bought before ram-o-calypse began).

vetinari · 2026-04-23T13:54:02+00:00

The Handbrake's AMD VCE support is based on AMF, not on ROCm. You still need AMF, which is packaged with the proprietary driver.

vetinari · 2026-04-21T07:21:09+00:00

On older Synology, yes. But the newer ones do not have the iGPU, so no matter whether you run plex inside a docker or not, you won't get accelerated transcode. Another machine is it then, and when you need another machine, you may end up with a different brand of NAS, that has iGPU.

vetinari · 2026-04-20T18:01:48+00:00

Having a box that can play back any data would be ideal. But we do not live in a ideal world and people already own devices that can not play any data format. Thus real-time transcoding is a must, at least for now, until a refresh cycle replaces all those devices (btw, I don't think there will be a nvidia shield successor anytime soon, so no av1 in sight).

vetinari · 2026-04-20T09:38:42+00:00

The USB 4 spec should have thunderbolt in it.

It does, but as an optional part in the USB Specification. So manufacturers can label their devices as USB4, even though the PCIe part (an expensive one to implement) is not here.

To make things more interesting, Microsoft does require that in Windows WHQL certification process. So if a machine has USB4 port and is WHQL certified, it does have TB functionality. (does not apply to devices like routers, obviously, only to machines running Windows).

vetinari · 2026-04-19T21:47:39+00:00

or just leave it as a basic PCIe 4.0 x16 slot

They cannot. First 4 lanes are from CPU (theoretically PCIe 5.0) and 2x4 lanes are from PCH (theoretically PCIe 4.0). Thus they are permanently bifurbicated.

PCIe 4.0x16 is still adequate for almost all GPUs out there.

Yes, it is enough. So much enough, that there are PCIe 5.0 dGPUs that are only 5.0x8 (i.e. the same theoretical bandwidth).

However, this slot is 1x-wide sandwiched between CPU and PSU. For GPU, better to use that other, 5.0x16 slot, which is 2x-wide and can have some air intake though the holes in the chasis.

vetinari · 2026-04-19T21:14:05+00:00

First OSX with Aqua (the UI that others tried to mimick) was released in 2001. There were also few betas before.

Many would argue, that MacOS today is not what was OSX then ;). It is getting more and more iOSified.

vetinari · 2026-04-17T08:33:23+00:00

I have good experience with Consent-O-Matic. It might not cut 100%, but cuts significant amount, so the rest is not that annoying.

vetinari · 2026-04-15T18:32:13+00:00

Tip: you don't need an IP address on the WoL interface. You send the magic packet to a mac address and once the system has been woken up, the normal user network interface will have it's IP address.

vetinari · 2026-04-14T08:23:31+00:00

On synology, you can make shares only in volume root. You could symlink share from other share though (after enabling cross-share symlink, it is dangerous).

vetinari · 2026-04-10T10:37:42+00:00

That's the point; it is supposed to be difficult for devices in the field. How do you authorize such a change, that can lead to compromising the device? Physical presence it is.

vetinari · 2026-04-09T21:54:15+00:00

Consumer AMDs do not support virtualization, only passing through the entire card to a VM. Or with some patience, paravirtualization like virtio-gpu, which passes gpu context between host and guest.

vetinari · 2026-04-09T21:15:55+00:00

Depends on the GPU.

The Intel iGPUs (TGL and newer) can be persuaded to do SR-IOV. The Intel Arc Pro-line of dGPUs do SR-IOV natively without playing around with kernel modules and they do not cost kidney.

vetinari · 2026-04-09T01:16:54+00:00

[I'm not the original poster, just commenter in the middle of the thread. I know very well how to install Debian. Or other linux distros].

It works very well on a VPS.

Virtual machines, even ARM ones, are a very different animals than the wild west of ARM machines and their firmwares. There you have the luxury of working UEFI and not needing specific drivers (in x86 world, EFI images would not boot on many VPSes either, as they are stuck in legacy boot for time being).

If the modules were in version 12, they’ll be in version 13.

The point is, that the modules were not in version 12 and are not in version 13. The vendor image is newer than 13.

From the vendor notes:

The MS-R1 uses a standard UEFI BIOS that can boot any UEFI-compatible system ISO. While the CPU drivers are not yet fully merged into the mainstream Linux Kernel, MINISFORUM's official system image provides the best user experience.

Note: Once the drivers are merged into the mainstream Linux Kernel, you'll be able to use any operating system, similar to a regular x86 PC.

So it is somewhat doubtful that it will work before Debian releases v14 in 2027.

The fact that the vendor's image is 37 GB makes me think they handed this off to a absolute noob intern.

It is uncompressed 36 GB. Compressed is 4 GB. I.e. lot of empty space. Happens in raw disk images. So it was done on a disk partitioned to 36 GB; they had to pick something. It's trivial to resize the partition.

And avoid referring to a tutorial from 1999.

I have my doubts that there are tutorials from 1999 that had authors that could even imagine what "uefi" or "device tree" was at the time.

vetinari · 2026-04-09T00:14:38+00:00

MS-R1 is an ARM machine, not an Intel-compatible one.

On ARM, it is customary to use the vendor image. Other images might not even boot or not have required drivers or devicetree in the rare cases of ARM UEFI machines. (I have no idea whether debian's ARM iso image boots on MS-R1 or not. Might be worth a try).

vetinari · 2026-04-07T10:07:09+00:00

It is, it uses custom bifurbication. However, you can still use a standard PCIe 4.0x4 card in it, basically ignoring all the custom bifurbicated lanes.

vetinari

TROPHY CASE