Selfhosted

39937 readers

410 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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Anyone hosting pixelfed using docker? (kerala.party)

submitted 1 year ago* (last edited 1 year ago) by A10@kerala.party to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

Hi I am finding it extremely frustrating that the provided docker compose does not work. and documentation is non existent for docker pixelfed installation. Does the internal/external networking ever work? What file/folder permissions I have to set? Please help.

Sorry for the ranting.

Here is what I have tried so far

this is the docker compose I used, https://github.com/pixelfed/pixelfed/blob/dev/docker-compose.yml

Problem 1: pixelfed/pixelfed:latest does not exist, I am using quay.io/zknt/pixelfed:latest after going through github issues.

Problem 2: The app container cannot find the db container. DNS resolution based on the docker compose service name is not working in my case. I also faced similar issues when trying to selfhost lemmy, ended up removing all external, internal networking before it worked for me.

Solved: https://gitea.com/NoobA10/federated-services-docker-ansible

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

[–] Still@programming.dev 2 points 1 year ago (1 children)

so in socker compose external tetwork is a network created outside of that compose file, for example on setup I have traefik running in a container which defines the traefik network, in another compose file you can reference that network by name and mark it as external to connect containers to it

I've not set up a pixelfed instance before so I can't help with the folder perms but I'd think they would work themselves out

[–] A10@kerala.party 1 points 1 year ago* (last edited 1 year ago) (1 children)

thanks for your reply. This is how it is defined in the docker compose file I used. AFAIK When using the internal network, the ports are exposed to an internal subnet and no port mapping is necessary.

  internal:
    internal: true
  external:
    driver: bridge

[–] Still@programming.dev 1 points 1 year ago

no no internal: true mans the network is isolated from the outside and is irrelevant to needing port mapping or not, poet mapping is only needed to bring traffic into the docker virtual network

for my setup I have only one container with port mapping running traefik reverse proxying to my other sevices which use the external:true network because it is managed by the traefik docker compose file, in the traefik compose I do not say external: or internal: