Selfhosted

63,708 readers

5,296 active

445 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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

moderation log

moderators

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Anybody running IncusOS here? (linuxcontainers.org)

submitted 2 weeks ago by TheBigRoomXXL@leminal.space to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

I discovered Incus and IncusOS recently, and they seem like a very cool foundation for a self-hosted setup.

I'm thinking of using them with incus-compose to declare my setup.

Does anybody use them? I'd love to get some feedback. Are they stable and polished yet, or are there still a lot of sharp edges?

They mention "designed for modern systems" on their website. Are there any issues running it on a roughly 10-year-old laptop?

you are viewing a single comment's thread
view the rest of the comments

[–] muusemuuse@sh.itjust.works 1 point 2 weeks ago

I didn’t follow the instructions carefully enough and the installer bricked a motherboard by incorrectly enrolling secure boot keys. The board doesn’t have dual bios or a way to flash without POST, the SPI has to be removed, flashed, and resoldered, which surprised me that gigabyte would not have a recovery plan in place across all their boards but that’s my fault for not checking what I bought.

TLDR: read the instructions in their guide carefully. You can brick a board with this.

permalink

fedilink

source