Hey, does anyone else have issues running a lemmy instance with docker compose?
I cant get it to work. I followed the guide on the wiki step by step to no avail…
Edit: This is my error message with the docker-compose config as provided by the guide:
Then I tried to remove the logging bits, I get this error:
Then I started over and pulled the github repository and edited the files in the docker subfolder and I get this error:
I give up 🙂
I used the docker-compose file from the official github repo: https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
But after the comment from @marsara9@lemmy.world I changed it to pull the image from dockerhub instead of building it myself. Now it pulls correctly and the server comes online but is almost unusable. The homepage displays but I cannot login as admin or create a new user :/
Edit: Here is the docker-compose.yml I used
Edit 2: I think I found the issue why the server is unusable. I have websocket errors
Also, @hyper@lemmy.ml, what does your nginx.conf look like? Now that the webpage is loading, the backend might be blocked/not configured properly in nginx, so nginx isn’t properly forwarding requests to the backend.
Don’t pull dev use 0.17.4
lemmy: image: dessalines/lemmy:dev
lemmy: image: dessalines/lemmy:0.17.4
Also in your Pictrs environment you may need:
- PICTRS__SERVER__ADDRESS=0.0.0.0:8080
Lastly did you do the following before runing your docker-compose up -d cmd?
mkdir -p volumes/pictrs sudo chown -R 991:991 volumes/pictrs
3rd reply :)
Have you edited your lemmy.hjson yet to ensure details match the docker-compose.yml? The instructions for that part are not very clear and I had to do lots of trial and error to get it working.
I had a similar issue, use a more recent version of the lemmy-ui image. I used “latest” and it worked
2nd reply, can you also post the logs from the lemmy-lemmy-1, lemmy-lemmy-ui-1, lemmy-postgres-1, and lemmy-pictrs-1 containers?
I found most of my issues were dealing with communication between networks and IP’s binding wrong which wont show anywhere but in the logs as connection issues.