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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed
Self Hosted - Self-hosting your services. @lemmy.ml ch00f @lemmy.world “docker compose run” isn’t doing what I think it’s supposed to
I’m running funkwhale in docker. This consists of a half dozen docker containers one of which is postgres.
To run a backup, funkwhale suggests shutting down all of the containers and then docker compose running pg_dump on the postgres container. Presumably this is to copy the database when nobody is accessing it.
For some reason when I do this, I get an error like:
undefined
pg_dump: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket?It would seem that postgres isn’t running. I see the same error with other commands such as psql.
If I fully boot the container and then try exec-ing the command, it works fine.
So it would seem that the run command isn’t fully booting the instance before running the command? What’s going on here?
The container is built from postgres:15-alpine