You can attach these containers to “host” networking, which will allow you to do simple port addressing, like you would with a non-containerized host. Run X on 8080, run Y on 9999, etc. Applies to both rkt and Docker.
rkt networking docs: https://coreos.com/rkt/docs/latest/networking/overview.html#host-mode - Rob > On Jul 18, 2016, at 9:22 AM, Florian Koch <[email protected]> wrote: > > why not run these apps in a pod? > > 2016-07-18 17:00 GMT+02:00 Derek Mahar <[email protected]>: >> On Friday, 4 March 2016 14:18:59 UTC-5, Alex Crawford wrote: >>> >>> On 03/04, [email protected] wrote: >>>> 1) Does either or both etcd and/or fleet actually need to be running on >>>> a >>>> standalone host? Are they so integral to CoreOS that they must be used? >>> >>> Nope. I have a standalone host that runs a few services. I don't actually >>> use >>> etcd or fleet since there is no cluster. >> >> >> Do you run your services in Docker or rkt containers? If using rkt, what >> kind of networking do you use and how do you configure your containers to >> talk to each other? >> >> I wish to run rkt containers for vpnc, ActiveMQ, PostgreSQL server, Tomcat, >> and a standalone Java application on a single CoreOS host, but am unsure how >> the Tomcat and the Java application containers can address the shared >> ActiveMQ and PostgreSQL server containers. A user on #coreos has told me >> that I must use service discovery, but this strikes me as overkill for a few >> containers that run on a single host. >> >> Any suggestions? >> >> Derek
