this post was submitted on 30 May 2024
421 points (95.7% liked)

Selfhosted

40677 readers
441 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
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[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] 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?

  1. Update the package index:

sudo pacman -Syu

  1. Install required dependencies:

sudo pacman -S docker

  1. Enable and start the Docker service:
sudo systemctl enable docker.service
sudo systemctl start docker.service
  1. Add your user to the docker group to run Docker commands without sudo:

sudo usermod -aG docker $USER

  1. 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

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

[–] [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.