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?
this post was submitted on 18 Jul 2023
13 points (88.2% liked)
Selfhosted
40296 readers
564 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
sorry for the rant, I have updated the post.
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.
Thanks I figured it out. And created an Ansible playbook https://gitea.com/NoobA10/federated-services-docker-ansible
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
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
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:
Do you use the ENV file, and can you post that? (No passwords)
view more: next ›