Conversation

Notices

1. Embed this notice
   novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 07:48:38 JST novatorine 🏴🏳️‍⚧️

   Hey does anyone know how to make it so that a server can curl or ping its own domain or public IP (without just editing that domain into the hosts file, since I Need a Doctor containers to be able to talk to the server as well so just editing the domain into the hosts file as localhost won't work on the containers bc for them localhost means themselves)? Been really stumped on this one

   • Embed this notice
     king toot uncommon (capn_b@mastodon.online)'s status on Tuesday, 17-Oct-2023 07:52:01 JST king toot uncommon

     in reply to

     @anarchopunk_girl is the problem that you don't know the public IP or that you can't ping the domain once you have the address?

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 07:52:01 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • king toot uncommon

     @capn_b oh I have both the public IP and the domain it just doesn't work, times out

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 07:55:14 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose oh god.... why can't the machine just talk to itself? AAAAAAA this is why I'm a software developer not a sysadmin this shit just hates you and wants you to die lmao

     I'll try doing sketchy shit with the docker IDs and see what happens I guess

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 07:55:15 JST :pdx_elk:

     in reply to

     @anarchopunk_girl if you don't want to edit the hosts file, then setting up custom DNS rules would probably be the next best solution. You could either run your own DNS server or use something like NextDNS.

     Each docker container should have an IP on an internal network (depending on the containers network settings).

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 07:58:26 JST :pdx_elk:

     in reply to

     @anarchopunk_girl it can on the localhost address like 127.0.0.1. Then you can expose the network ports from the containers as needed. Otherwise, you can use a virtual network between the host and containers.

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 07:58:26 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose what's going on is that I wanted two docker containers exposed on different ports on the server to talk to each other via just the server's web address and the relevant port, because the address is modifiable in one of the docker's web UIs. I can access the docker that's supposed to be contacted myself, but the actual docker that needs to talk to it can't.

   • Embed this notice
     king toot uncommon (capn_b@mastodon.online)'s status on Tuesday, 17-Oct-2023 08:00:32 JST king toot uncommon

     in reply to

     • :pdx_elk:

     @anarchopunk_girl @rose is this a docker-in-docker situation, or are the two containers running in different places?

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:00:32 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:
     • king toot uncommon

     @capn_b @rose side by side, I believe

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 08:03:01 JST :pdx_elk:

     in reply to

     @anarchopunk_girl If the two containers just need to talk to each other and not be publicly accessible, then you can actually network them together behind the scenes.

     This tutorial covers a lot of the options: https://www.tutorialworks.com/container-networking/

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:03:01 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose okay yeah using the other docker container's fake IP address works inside an exec bash at least, let us see if the web interface likes it (I bet it won't)

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:03:08 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose OH HOLY SHIT IT DID

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:05:00 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose well it's still borked but in a totally different way now! Progress! I hate nextcloud!

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 08:05:01 JST :pdx_elk:

     in reply to

     @anarchopunk_girl yeah, docker sets the host aliases to the virtual network automatically.

     Glad you got it working.

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:15:13 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose thank you! but idk if that'd help much. I'm trying to use next Cloud all in one which is a Docker container that sets up and runs like seven other Docker containers to get the whole thing including collabora setup it's just poorly documented and confusing

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 08:15:14 JST :pdx_elk:

     in reply to

     @anarchopunk_girl oh, it's next cloud. That was a nightmare to get setup. If you are using Collabora in a container ...

     I have a docker compose file for it if you want. It's ... complex.

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:16:36 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:

     @rose that seems like it'd be better but I'm in sunk cost territory now and I want to use the official recommended image

   • Embed this notice
     :pdx_elk: (rose@503junk.house)'s status on Tuesday, 17-Oct-2023 08:16:37 JST :pdx_elk:

     in reply to

     @anarchopunk_girl ah, mines a custom Docker Stack that launches multiple containers from the single Docker Compose file.

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 08:29:51 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • :pdx_elk:
     • archlentil

     @archlentil @rose this I what I'm using: https://github.com/nextcloud/all-in-one . It seems like it was the most logical choice because it's all of the relevant doctor containers assembled into a single system that you can manage through a web dashboard and stuff and it's got everything implemented even the stuff people commonly forgot to set up like redis

   • Embed this notice
     archlentil (archlentil@toots.a-deed.com)'s status on Tuesday, 17-Oct-2023 08:29:52 JST archlentil

     in reply to

     @anarchopunk_girl are you using the apache image or the fpm one?

   • Embed this notice
     novatorine 🏴🏳️‍⚧️ (anarchopunk_girl@kolektiva.social)'s status on Tuesday, 17-Oct-2023 11:38:01 JST novatorine 🏴🏳️‍⚧️

     in reply to

     • archlentil

     @archlentil it is in fact very cool!! it gives you a web-based dashboard to manage all of the docker containers necessary to actually run a full nextcloud instance, where you can enable and disable services with a checklist, and click to see the logs of each server in your browser, and use a graphical user interface to stop and restart and see the status of each container, and it'll even notify you when there are updates for your Docker containers as well! The only hitch is that if you try to set Collabora up according to what their docs say, it won't work. Instead follow this guide:

     https://help.nextcloud.com/t/nextcloud-all-in-one-docker-behind-router-and-reverse-proxy-cannot-talk-to-https-nextcloud-mydomain-com-hosting-capabilities-or-collabora-office/172269/10?u=alexispurslane

   • Embed this notice
     archlentil (archlentil@toots.a-deed.com)'s status on Tuesday, 17-Oct-2023 11:38:02 JST archlentil

     in reply to

     @anarchopunk_girl just realized I'm using the community maintained apache image on docker hub. the AIO one seems cool!