this post was submitted on 05 Jan 2025
34 points (90.5% liked)

Selfhosted

40923 readers
756 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
34
Is it possible to run a docker host that has no harddrive? (self.selfhosted)
submitted 1 day ago* (last edited 1 day ago) by Passerby6497 to c/selfhosted
43 comments fedilink hide all child comments
 

So I had a micro PC that was running one of my core services and it only supports NVMe drives. Unfortunately, this little guy cooked itself and I'm not in a position to replace the drive. The system is still good and is fairly powerful, so I want to be able to reuse it.

I'm thinking I want to set up some kind of netboot appliance on another server to be able to allow me to boot the system without ever having a local disk. One thing I want to is run some docker images (specifically Frigate) but i wont be able to write anything to persistent storage locally. NFS shares are common in my setup.

Is it even possible to make a 'gold image' of a docker host and have it netboot? I expect that memory limitations (16GB) will be my main issue, but I'm just trying to think of how to bring this system back into use. I have two NAS appliances that I can use for backend long term storage (where I keep my docker files and non-database files anyway), so it shouldn't be too difficult to have some kind of easily editable storage solution. I don't want to use USB drives as persistent storage due to lifespan concerns from using them in production environments.

you are viewing a single comment's thread
view the rest of the comments
[–] uranibaba 7 points 1 day ago (1 children)

How about running the OS from a USB stick? Put all images you want on it and mount NAS drives at boot.

[–] Passerby6497 1 points 1 day ago (1 children)

I'm leery about using a USB for long term persistent OS storage due to lifespan issues I've seen when just running a hypervisor from one. A 'real' usermode OS is probably going to have a worse lifespan than what I was seeing at work.

[–] Deckweiss 2 points 1 day ago* (last edited 1 day ago)

I have a raspberry pi running from a microsd (which uses the same kind of tech as a usb stick) for over 5 years with dietpi.

But considering that you think you chewed through an nvme somehow, you may be right.