Selfhosted

60320 readers

553 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Is it possible to run a docker host that has no harddrive? (lemmy.world)

submitted 2 years ago* (last edited 2 years ago) by Passerby6497@lemmy.world to c/selfhosted@lemmy.world

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

[–] Drusenija@aussie.zone 1 points 2 years ago (1 children)

I can't speak to the netboot part personally but I've had Docker data folders mounted via an NFS share for a while now, and while it worked fine, I've just in the last week or so swapped them all back to local storage for performance reasons (typically anything involving a SQLite database), so depending on what services you're running via Docker, check that your network speeds aren't going to be a bottleneck for it. (My home network is only 1G for reference so might not be a problem for you).

[–] Passerby6497@lemmy.world 1 points 2 years ago

Yeah, NFS bind mounts aren't an issue. The issue I run into is database lock errors when I try to write a database file to the NFS share. I've got 1G networking as well and haven't seen issues accessing regular files from my containers via the bind mounts.