Selfhosted

40199 readers

254 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

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

sorry for the rant, I have updated the post.

[–] killabeezio@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] A10@kerala.party 1 points 1 year ago

Thanks I figured it out. And created an Ansible playbook https://gitea.com/NoobA10/federated-services-docker-ansible