Glad you solved it! Definitely sounds like a better solution than playing around in the db

Oh yeah, try specifying the hostname as localhost (I think it’s -h, but --help will confirm it). Psql tries by default to connect to that socket, but in docker it does use it.

Basically, you’ll need to specify the hostname and user (and if port, which should just be default, then -p 5432)

It should be

docker exec -it lemmymydomain_postgres_1 psql -h localhost -U lemmy (dbname)

Keeping in mind that you’ll need to have the right user and database name, assuming (based on your original comment) lemmy being the username and the db name might also be lemmy

Edit: this should btw just get you into the db, I have no idea of its a good idea or not to delete a user directly from the db, it might cause issues, but I don’t have experience with it, but just generally use postgres in docker with other projects

You might be able to just run docker-compose exec postgres psql to drop into a shell (you may still need to define the user with -U lemmy)

If you’re trying to connect with ane external tool though, you’ll need to expose the ports temporarily, which I’m not sure if you can do without restarting the container (after adding the exposed ports to the docket compose file, like 127.0.0.1:5432:5432)

Oh thank you! I couldn’t figure out how to do it in the app I use (Liftoff) but with your comment I checked again and found out how!

This makes “All” so much better to explore, thank you!

It really annoys me, especially as there seems to be at least two lemmy instances that are 99% just a bot reposting everything from reddit… Really wish I could block whole instances