Merge pull request #19557 from akka/wip-18989-make-akka-with-docker-googlable-johanandren
=doc #18989 Make docs more googlable with regards to docker containers
This commit is contained in:
commit
7f52f54cd8
5 changed files with 20 additions and 8 deletions
|
|
@ -59,3 +59,15 @@ Use ``Ctrl-C`` to interrupt and exit the application.
|
|||
|
||||
On a Windows machine you can also use the ``bin\akka-sample-main-scala.bat`` script.
|
||||
|
||||
|
||||
In a Docker container
|
||||
=====================
|
||||
You can use both Akka remoting and Akka Cluster inside of Docker containers. But note
|
||||
that you will need to take special care with the network configuration when using Docker,
|
||||
described here: :ref:`remote-configuration-nat`
|
||||
|
||||
For an example of how to set up a project using Akka Cluster and Docker take a look at the
|
||||
`"akka-docker-cluster" activator template`__.
|
||||
|
||||
__ https://www.typesafe.com/activator/template/akka-docker-cluster
|
||||
|
||||
|
|
|
|||
|
|
@ -35,8 +35,8 @@ settings, but with ``akka.cluster.ClusterActorRefProvider``.
|
|||
The ``akka.cluster.seed-nodes`` should normally also be added to your ``application.conf`` file.
|
||||
|
||||
.. note::
|
||||
If you are using Docker or the nodes for some other reason have separate internal and external ip addresses
|
||||
you must configure remoting according to :ref:`remote-configuration-nat-java`
|
||||
If you are running Akka in a Docker container or the nodes for some other reason have separate internal and
|
||||
external ip addresses you must configure remoting according to :ref:`remote-configuration-nat-java`
|
||||
|
||||
The seed nodes are configured contact points for initial, automatic, join of the cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -475,8 +475,8 @@ There are lots of configuration properties that are related to remoting in Akka.
|
|||
|
||||
.. _remote-configuration-nat-java:
|
||||
|
||||
Remote configuration for NAT and Docker
|
||||
---------------------------------------
|
||||
Akka behind NAT or in a Docker container
|
||||
----------------------------------------
|
||||
|
||||
In setups involving Network Address Translation (NAT), Load Balancers or Docker
|
||||
containers the hostname and port pair that akka binds to will be different than the "logical"
|
||||
|
|
|
|||
|
|
@ -29,8 +29,8 @@ settings, but with ``akka.cluster.ClusterActorRefProvider``.
|
|||
The ``akka.cluster.seed-nodes`` should normally also be added to your ``application.conf`` file.
|
||||
|
||||
.. note::
|
||||
If you are using Docker or the nodes for some other reason have separate internal and external ip addresses
|
||||
you must configure remoting according to :ref:`remote-configuration-nat`
|
||||
If you are running Akka in a Docker container or the nodes for some other reason have separate internal and
|
||||
external ip addresses you must configure remoting according to :ref:`remote-configuration-nat`
|
||||
|
||||
The seed nodes are configured contact points for initial, automatic, join of the cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -480,8 +480,8 @@ There are lots of configuration properties that are related to remoting in Akka.
|
|||
|
||||
.. _remote-configuration-nat:
|
||||
|
||||
Remote configuration for NAT and Docker
|
||||
---------------------------------------
|
||||
Akka behind NAT or in a Docker container
|
||||
----------------------------------------
|
||||
|
||||
In setups involving Network Address Translation (NAT), Load Balancers or Docker
|
||||
containers the hostname and port pair that akka binds to will be different than the "logical"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue