Selfhosted

40677 readers

525 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 posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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 2 years ago

MODERATORS

[email protected]

421

Why You Should Self-Host Everything (dev.to)

submitted 6 months ago by [email protected] to c/[email protected]

164 comments fedilink hide all child comments

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

[–] [email protected] 8 points 6 months ago (1 children)

Honestly at this point that is docker and docker compose.

As to what to run it on that very much depends on preference. I use a proxmox server but it could just as easily be pure Debian. A basic webui like cockpit can make system management operations a bit more simplified.

[–] [email protected] 2 points 6 months ago (1 children)

Docker is in theory nice, if it works. Docker doesn't run on my computer(i have no fucking clue why). Every time I try to do anything I get the Error "Unknown Server: OS" also there is literally nothing you can find online about how to Fux this problem.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago) (1 children)

What computer and OS do you have that can't run docker? You can run a full stack of services on a random windows laptop as easily as a dedicated server.

Edit

Autocorrect messing with OS.

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago) (1 children)

I use EndeavourOS, but had the same problem on Arch.

Hardware wise I have an 75800x, a RX 6700XT and 32GB 3200mhz Ram.

The weird thing is, that some time ago I was actually able to use docker, but now I'm not.

[–] [email protected] 1 points 6 months ago (2 children)

That doesn't make any sense to me. It can be installed directly from pacman. It may be something silly like adding docker to your user group. Have you done something like below for docker?

Update the package index:

sudo pacman -Syu

Install required dependencies:

sudo pacman -S docker

Enable and start the Docker service:

sudo systemctl enable docker.service
sudo systemctl start docker.service

Add your user to the docker group to run Docker commands without sudo:

sudo usermod -aG docker $USER

Log out and log back in for the group changes to take effect.

Verify that Docker CE is installed correctly by running:

docker --version

If you get the above working docker compose is just

sudo pacman -S docker-compose

[–] [email protected] 1 points 6 months ago (1 children)

sudo pacman -S docker-compose

I did all the steps you mentioned and now it works(at least if use sudo to run the commands).

[–] [email protected] 1 points 6 months ago

I thought it would. If it still requires sudo to run it is probably just docker wanting your user account added to the docker group. If the "docker" group doesn't exist you can safely create it.

You will likely need to log out and log back in for the system to recognize the new group permissions.

[–] [email protected] 1 points 6 months ago

I didnt start docker and didn't add it to my user group. Maybe this will fix it.