robolemmy

I'm using a docker compose file, and I have everything running just fine, containers talking to each other as needed, NPM reverse proxying everything via a duckdns subdomain... everything's cool.

Problem is, I can still go to, for example, http://192.168.1.30:8080/ and get the services without http.

I've tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.

Any advice for me?

Edit:

Thanks for the quick & helpful suggestions!

While investigating bridge networks, I noticed a mention that containers could only find each other on the default container bridge by container name, which I did not know. I had tried 127.0.0.1, localhost, the external IP, hostnames, etc but not container names.

In the end, the solution was just to use container names when telling each container how to find the others. No need for creating bridge networks or any other shenanigans.

Thank you!

I like this one better than the more recent American version with Gere and Lopez.

I'm currently using an AMD 5950x and an Nvidia GeForce RTX 3080 LHR, pushing video to a Dell U4021QW, which is a 40" monitor running 5120x2160@60hz. A few of the games I play are pretty challenged at that resolution, so I'm thinking of upgrading at least the video card. Is there any reason to build a new system with a newer CPU as well?

Somebody said we needed more Nick Cave.

I have a lovely plex server set up and working very well, with tons of content ready to play. Now I just need a client for my TV that doesn't piss me off. I absolutely detest Google/Android TV, and my Apple TV periodically wipes out my Plex preferences, which is a known issue.

I'd like to have a 100% dedicated plex client for my TV. I don't want or need it to do anything else at all, and it has to be totally remote friendly and capable of playing 4k/60 UHD content.

Any suggestions?