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

  • killabeezio@lemmy.worldEnglish
    4·
    1 year ago

    Not sure what pixelfed is, but you yelling I need help doesn’t really help anyone. What problems are you having exactly. What image are using? What commands are running? What have you tried?

      • killabeezio@lemmy.worldEnglish
        1·
        1 year ago

        I don’t even know if that’s being maintained. I couldnt find anything on docker hub. It does look like this one is maintained though https://blog.pixelfed.de/2020/05/29/pixelfed-in-docker/

        Maybe give that one a try. It seems like you are already using his image anyway. Also it seems like the command to run for the worker is different in his image.

        If you have issues with that setup, feel free to post what issues you having.

        Technically you don’t really need to setup a bunch of networks unless you are trying to host this or something, which I wouldn’t recommend docker compose anyway. So, if you wanted to keep it simple, you could just the default network.

        Another note, while zknt/pixelfed does exist on docker hub. It was moved to quay, so continue using that image.

  • Still@programming.devEnglish
    2·
    1 year ago

    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@kerala.partyOPEnglish
      1·
      1 year ago

      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.devEnglish
        1·
        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: