Selfhosted

60024 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

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 1 year ago* (last edited 1 year 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

[–] thumdinger@lemmy.world 8 points 1 year ago* (last edited 1 year ago) (1 children)

You mention frigate specifically. Were you running this on the system when the drive failed, or is this a future endeavour?

I bring this up because I also use frigate, and for some time I was running with a misconfigured docker compose that drove my SSD wearout to 40% in a matter of months.

Make sure that the tmpfs is configured per the frigate documentation and example config. If misconfigured like mine was, all of that IO is on disk. I believe the ramdisk is used for temp storage of camera streams, until an event occurs and the corresponding clip is committed to disk.

Good luck!

[–] Passerby6497@lemmy.world 3 points 1 year ago

Interesting, it was running on this system, so it may actually have been wear that killed the drive. I'll have to look into that config and see if it's worth getting a new nvme to throw into the cook box.

Thanks for that info!