David, I do have SWARM active, and both containers are (or were) connected. Ive tried creating an overlay network, and connecting the container to it, but still no luck. In fact, I couldn’t even reach RTE from my browser to get a 3270 session. I just don’t have enough personal experience to come up with the correct incantation needed to make the bits flow….
Like I said, RTE is picking up the internal local IP, not the host IP, and the internal IP is only known inside the zcx container. Timothy, what you suggest could work, but my preference is to find the solution with “in-the-box” configuration? Dave Jousma Vice President | Director, Technology Engineering From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of David Crayford <dcrayf...@gmail.com> Date: Wednesday, November 8, 2023 at 9:00 AM To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: Anyone with zCX docker hands on? > On 8 Nov 2023, at 9: 36 pm, Timothy Sipples <sipples@ SG. IBM. COM> wrote: > > > Dave Jousma wrote: > >> Thanks Timothy. Yep found all that, have the > instance up and working just fine > >> it’s the peer to peer What software are you referring to, Docker? That’s fundamental to how Docker networking works. Publishing ports using “-p <portnum>” doesn’t make the services discoverable in docker containers. You meed overlay networking. TE Web is a typical clustering architecture using active/passive HA. You will also find that you can not run curl from within a Docker image. Most docker containers are built to take up as small a footprint as necessary so utilities like curl are not installed and you cannot instal them using apt if security keys are not enabled, which is best practice. > > (“Thinking out loud...”) Could you run a “bigger” Linux container image that > includes a VPN tunnel (such as WireGuard) to connect these two peers with one > another to work around the issue? Why not just use a Docker clustering such as swarm instead of hacking together solutions that don’t work? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
