|
|
| (125 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | + | [[Docker basic]] |
| | | | |
| − | =Manage Virtual Hosts with docker-machine=
| + | [[Docker Compose]] |
| − | <br>
| |
| − | ==Introduction==
| |
| − | https://docs.docker.com/machine/overview/
| |
| − | Docker Machine is a tool that lets you install Docker Engine on virtual hosts, and manage the hosts with docker-machine commands. You can use Machine to create Docker hosts on your local Mac or Windows box, on your company network, in your data center, or on cloud providers like Azure, AWS, or Digital Ocean. | |
| | | | |
| − | Using docker-machine commands, you can start, inspect, stop, and restart a managed host, upgrade the Docker client and daemon, and configure a Docker client to talk to your host.
| + | [[Docker Machine]] |
| − | :[[File:ClipCapIt-180622-224748.PNG]]
| |
| | | | |
| − | When people say “Docker” they typically mean Docker Engine, the client-server application made up of the Docker daemon, a REST API that specifies interfaces for interacting with the daemon, and a command line interface (CLI) client that talks to the daemon (through the REST API wrapper). Docker Engine accepts docker commands from the CLI, such as docker run <image>, docker ps to list running containers, docker image ls to list images, and so on.
| + | [[Docker Swarm Classic]] |
| | | | |
| − | '''Docker Machine''' is a tool for provisioning and managing your Dockerized hosts (hosts with Docker Engine on them). Typically, you install Docker Machine on your local system. Docker Machine has its own command line client docker-machine and the Docker Engine client, docker. You can use Machine to install Docker Engine on one or more virtual systems. These virtual systems can be local (as when you use Machine to install and run Docker Engine in VirtualBox on Mac or Windows) or remote (as when you use Machine to provision Dockerized hosts on cloud providers). The Dockerized hosts themselves can be thought of, and are sometimes referred to as, managed “machines”.
| + | [[Docker Swarm Mode]] |
| | | | |
| | + | [[Docker Swarm management]] |
| | | | |
| | + | [[Docker volume orchestration]] |
| | | | |
| | + | [[Docker Swarm on AWS]] |
| | | | |
| − | ==Hypervisor drivers==
| + | [[Stateful load-balancing in swarm]] |
| − | <br>
| |
| − | ===What is a driver===
| |
| − | Machine can be created with the '''docker-machine create''' command.
| |
| − | Most simple usage:
| |
| − | <pre>
| |
| − | docker-machine create -d <hybervisor driver name> <driver options> <machine name>
| |
| − | </pre>
| |
| | | | |
| − | The default value of the driver parameter is "virtualbox".
| + | [[Centralized logging in swarm]] |
| | | | |
| − | '''docker-machine''' can create and manage virtual hosts on the local machine and on remote clouds. Always the chosen driver determines where and how the virtual machine will be created. The guest operating system that is being installed on the new machine is also determined by the hypervisor driver. E.g. with the "virtualbox" driver you can create machines locally using the boot2docker as the guest OS.
| + | [[Metrics and Monitoring in swarm]] |
| | | | |
| − | The driver also determines the virtual network types and interfaces types that are created inside the virtual machine. E.g. the KVM driver creates two virtual networks (bridges), one host-global and one host-private network.
| + | [[Auto-scaling swarm]] |
| | | | |
| − | In the '''docker-machine create''' command, the available driver options are also determined by the driver. You always has to check the available options at the vandor of driver. For cloud drivers typical options are the remote url, the login name and the password. Some driver allows to change the guest OS, the CPU number or the default memory.
| + | [[Kafka with ELK on swarm]] |
| | | | |
| − | Here is a complete list of the currently available drivers: https://github.com/docker/docker.github.io/blob/master/machine/AVAILABLE_DRIVER_PLUGINS.md
| + | [[Java EE application with docker]]<br> |
| − | <br> | + | Itt egy tipikus, produkciós docker architektúrát mutatunk be egy két lábas JBoss cluster-el, de swarm nélkül |
| − | <br>
| |
| − | ===KVM driver===
| |
| | | | |
| − | KVM driver home page: https://github.com/dhiltgen/docker-machine-kvm
| + | [[Java EE application with swarm]]<br> |
| | + | Egy lehetséges production grade swarm architektúra telepített Java EE alkalmazás kialakítását mutatjuk be. |
| | | | |
| − | Minimum Parameters:
| |
| − | * --driver kvm
| |
| − | * --kvm-network: The name of the kvm virtual (public) network that we would like to use. If this is not set, the new machine will be connected to the '''"default"''' KVM virtual network.
| |
| | | | |
| − | '''Images''':<br>
| + | <br> |
| − | By default docker-machine-kvm uses a boot2docker.iso as guest os for the kvm hypervisior. It's also possible to use every guest os image that is derived from boot2docker.iso as well. For using another image use the --kvm-boot2docker-url parameter.
| + | =Docker on Fedora 31= |
| | + | https://www.reddit.com/r/linuxquestions/comments/dn2psl/upgraded_to_fedora_31_docker_will_not_work/<br> |
| | + | https://fedoraproject.org/wiki/Changes/CGroupsV2<br |
| | + | A Fedora31-ben bevezették a CGroupsV2-t amit a docker még nem követett le, ezért a docker a CGroupsV2-vel nem fog működni, ki kell kapcsolni. |
| | | | |
| − | '''Dual Network''':<br>
| |
| − | * '''eth1''' - A host private network called docker-machines is automatically created to ensure we always have connectivity to the VMs. The docker-machine ip command will always return this IP address which is only accessible from your local system.
| |
| − | * '''eth0''' - You can specify any libvirt named network. If you don't specify one, the "default" named network will be used.
| |
| − | If you have exotic networking topolgies (openvswitch, etc.), you can use virsh edit mymachinename after creation, modify the first network definition by hand, then reboot the VM for the changes to take effect.
| |
| − | Typically this would be your "public" network accessible from external systems
| |
| − | To retrieve the IP address of this network, you can run a command like the following:
| |
| − | docker-machine ssh mymachinename "ip -one -4 addr show dev eth0|cut -f7 -d' '"
| |
| | | | |
| − | Driver Parameters:<br>
| + | 1- |
| − | *--kvm-cpu-count Sets the used CPU Cores for the KVM Machine. Defaults to 1 .
| |
| − | *--kvm-disk-size Sets the kvm machine Disk size in MB. Defaults to 20000 .
| |
| − | *--kvm-memory Sets the Memory of the kvm machine in MB. Defaults to 1024.
| |
| − | *--kvm-network Sets the Network of the kvm machinee which it should connect to. Defaults to default.
| |
| − | *--kvm-boot2docker-url Sets the url from which host the image is loaded. By default it's not set.
| |
| − | *--kvm-cache-mode Sets the caching mode of the kvm machine. Defaults to default.
| |
| − | *--kvm-io-mode-url Sets the disk io mode of the kvm machine. Defaults to threads.
| |
| | | | |
| − | <br>
| + | vim /etc/default/grub |
| − | ==Install softwares== | + | 2- Add Line below in GRUB_CMDLINE_LINUX systemd.unified_cgroup_hierarchy=0 |
| − | | |
| − | First we have to install the docker-machine app itself:
| |
| | <pre> | | <pre> |
| − | base=https://github.com/docker/machine/releases/download/v0.14.0 &&
| + | GRUB_TIMEOUT=5 |
| − | curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
| + | GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" |
| − | sudo install /tmp/docker-machine /usr/local/bin/docker-machine
| + | GRUB_DEFAULT=saved |
| | + | GRUB_DISABLE_SUBMENU=true |
| | + | GRUB_TERMINAL_OUTPUT="console" |
| | + | GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-42aca868-45a4-438e-8801-bb23145d978d rd.lvm.lv=fedora_localhost-live/swap rhgb quiet systemd.unified_cgroup_hierarchy=0" |
| | + | GRUB_DISABLE_RECOVERY="true" |
| | + | GRUB_ENABLE_BLSCFG=true |
| | </pre> | | </pre> |
| | | | |
| | + | 3- Then : |
| | | | |
| − | Secondly we have to install the hypervisor driver for the docker-machine to be able to create, manage Virtual Machines running on the hypervisor. As we are going to use the KVM hypervisor, we have to install the "docker-machine-driver-kvm" driver:
| + | # grub2-mkconfig |
| − | <pre>
| + | |
| − | # curl -Lo docker-machine-driver-kvm \ | + | 4- Restart your PC |
| − | https://github.com/dhiltgen/docker-machine-kvm/releases/download/v0.7.0/docker-machine-driver-kvm \
| |
| − | && chmod +x docker-machine-driver-kvm \
| |
| − | && sudo mv docker-machine-driver-kvm /usr/local/bin
| |
| − | </pre>
| |
| | | | |
| − | We suppose that KVM and the libvirt is already installed on the system.
| |
| − | {{tip|If you want to use VirtualBox as your hypervisor, no extra steps are needed, as its docker-machine driver is included in the docker-machine app}}
| |
| | | | |
| | | | |
| − | Available 3rd party drivers: <br>
| |
| − | https://github.com/docker/docker.github.io/blob/master/machine/AVAILABLE_DRIVER_PLUGINS.md
| |
| − | <br>
| |
| − | <br>
| |
| | | | |
| − | ==Create machines with KVM==
| |
| | | | |
| − | ===Create the machine===
| |
| | | | |
| − | Before a new machine can be created with the docker-machine command, the proper KVM virtual network must be created.
| |
| | | | |
| − | See [[KVM#Add_new_networ|How to create KVM networks]] for details.
| |
| | | | |
| − | <pre> | + | <br> |
| − | # docker-machine create -d kvm --kvm-network "docker-network" manager
| |
| | | | |
| − | Running pre-create checks...
| |
| − | Creating machine...
| |
| − | (manager) Copying /root/.docker/machine/cache/boot2docker.iso to /root/.docker/machine/machines/manager/boot2docker.iso...
| |
| − | Waiting for machine to be running, this may take a few minutes...
| |
| − | Detecting operating system of created instance...
| |
| − | Waiting for SSH to be available...
| |
| − | Detecting the provisioner...
| |
| − | Provisioning with boot2docker...
| |
| − | Copying certs to the local machine directory...
| |
| − | Copying certs to the remote machine...
| |
| − | Setting Docker configuration on the remote daemon...
| |
| − | Checking connection to Docker...
| |
| − | Docker is up and running!
| |
| − | To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env manager
| |
| − | </pre>
| |
| | | | |
| − | {{tip|The machine is created under '''/USER_HOME/.docker/machine/machines/<machine_name>''' directory
| |
| | | | |
| − | If the new VM was created with virtualbox driver, the VirtualBox graphical management interface must be started with the same user, that the VM was created with, and the VirtualBox will discover the new VM automatically}}
| |
| | | | |
| − | ===Check what was created===
| |
| − | <br>
| |
| − | ====Interfaces on the host====
| |
| − | <pre>
| |
| − | # ifconfig
| |
| − | eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
| |
| − | inet 192.168.0.105 netmask 255.255.255.0 broadcast 192.168.0.255
| |
| − | ....
| |
| − | virbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
| |
| − | inet 192.168.42.1 netmask 255.255.255.0 broadcast 192.168.42.255
| |
| − | ...
| |
| − | virbrDocker: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
| |
| − | inet 192.168.123.1 netmask 255.255.255.0 broadcast 192.168.123.255
| |
| − | inet6 2001:db8:ca2:2::1 prefixlen 64 scopeid 0x0<global>
| |
| − | ...
| |
| − | </pre>
| |
| − | On the host, upon the regular interfaces, we can see the two bridges for the two virtual networks:
| |
| − | * '''virbrDocker''': That is the virtual network that we created in libvirt. This is connected to the host network with NAT. We assigned these IP addresses, when we defined the network.
| |
| − | * '''virbr1''': That is the host-only virtual network that was created out-of-the-box. This one has no internet access.
| |
| − | <br>
| |
| | | | |
| − | ====Interface the new VM====
| |
| − | You can log in to the newly created VM with the '''docker-machine ssh <machine_name>''' command
| |
| − | On the newly created docker ready VM, four interfaces were created.
| |
| − | <pre>
| |
| − | # docker-machine ssh manager
| |
| − | ## .
| |
| − | ## ## ## ==
| |
| − | ## ## ## ## ## ===
| |
| − | /"""""""""""""""""\___/ ===
| |
| − | ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
| |
| − | \______ o __/
| |
| − | \ \ __/
| |
| − | \____\_______/
| |
| − | _ _ ____ _ _
| |
| − | | |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __
| |
| − | | '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |
| − | | |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ |
| |
| − | |_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
| |
| − | Boot2Docker version 18.05.0-ce, build HEAD : b5d6989 - Thu May 10 16:35:28 UTC 2018
| |
| − | Docker version 18.05.0-ce, build f150324
| |
| − | </pre>
| |
| − | <br>
| |
| − | Check the interfaces of the new VM:
| |
| − | <pre>
| |
| − | docker@manager:~$ ifconfig
| |
| − | docker0 inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
| |
| − | ...
| |
| − | eth0 inet addr:192.168.123.195 Bcast:192.168.123.255 Mask:255.255.255.0
| |
| − | ...
| |
| − | eth1 inet addr:192.168.42.118 Bcast:192.168.42.255 Mask:255.255.255.0
| |
| − | </pre>
| |
| − | * '''eth0''':192.168.123.195 - Interface to the new virtual network (docker-network) created by us. this network is connected to the host network,so it has public internet access as well.
| |
| − | * '''eth1''':192.168.42.118 - This connect to the dynamically created host-only virtual network. Just for VM-to-VM communication
| |
| − | * '''docker0''':172.17.0.1 - This VM is ment to host docker container, so the docker daemon was already installed and started on it. Form docker point of view, this VM is also a (docker) host, and therefore the docker daemon created the default virtual bridge, that the containers will be connected to unless it is specified implicitly otherwise during container creation.
| |
| − | <br>
| |
| − | Inspect the new VM with the '''docker-machine inspect''' command
| |
| − | <pre>
| |
| − | # docker-machine inspect manager
| |
| − | {
| |
| − | "ConfigVersion": 3,
| |
| − | "Driver": {
| |
| − | ....
| |
| − | "CPU": 1,
| |
| − | "Network": "docker-network",
| |
| − | "PrivateNetwork": "docker-machines",
| |
| − | "ISO": "/root/.docker/machine/machines/manager/boot2docker.iso",
| |
| − | "...
| |
| − | },
| |
| − | "DriverName": "kvm",
| |
| − | "HostOptions": {
| |
| − | ....
| |
| − | },
| |
| − | "SwarmOptions": {
| |
| − | "IsSwarm": false,
| |
| − | ...
| |
| − | },
| |
| − | "AuthOptions": {
| |
| − | ....
| |
| − | }
| |
| − | },
| |
| − | "Name": "manager"
| |
| − | }
| |
| − | </pre>
| |
| − | <br>
| |
| | | | |
| − | ====Routing table==== | + | =Swarm Classic VS Swarm mode= |
| | + | Docker has been innovating at quite a dramatic pace, and focussing on making their technology easier to deploy, and applicable for a wider range of use cases. One of the features that has received the highest level of focus is Clustering/Orchestration. In Docker language, that means Swarm. |
| | | | |
| − | <pre>
| + | source: https://www.linkedin.com/pulse/docker-swarm-vs-mode-neil-cresswell/ |
| − | All the packages that ment to go to the docker VMs are routed to the bridges
| |
| − | # route
| |
| − | Kernel IP routing table
| |
| − | Destination Gateway Genmask Flags Metric Ref Use Iface
| |
| − | ... | |
| − | 192.168.42.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr1 <<<<this
| |
| − | 192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 virbrDocker <<<this
| |
| − | </pre>
| |
| − | <br>
| |
| − | ====IPtables modifications====
| |
| | | | |
| | + | ==Swarm classic== |
| | + | Prior to Docker 1.12 Swarm (Classic) existed as a standalone product, it relied on a complicated setup of external service discovery systems (eg consul) and a dedicated set of containers which ran as the swarm controllers. Load balancing network traffic across containers required external load balancers, and these needed to be integrated with service discovery to function correctly. Standalone Docker hosts were members of a swarm cluster, and the swarm controllers presented the pooled capacity from all hosts as a single “virtual” docker host. By presenting the swarm cluster as a virtual docker host meant that the way you interacted with Swarm was exactly the same way you interacted with a standalone host (docker run, docker ps, docker images, docker volumes), you just directed the commands (using –H=tcp://) at the swarm master IP:Port instead of individual swarm nodes. |
| | | | |
| − | :[[File:ClipCapIt-180623-010335.PNG|800px]]
| + | A Docker 1.12-es verziója előtt a Swarm (Classic) egy külön álló termék volt, nem volt része a docker engine-nek. A swarm-ot a docker engine-en futó swarm konténerekkel kellett létrehozni. Vo |
| | | | |
| | + | ==Swarm mode== |
| | + | Since releasing Docker 1.12, and embedding Swarm Mode (I really wish they had called it something else to minimise confusion) into the core Docker engine, the functionality and management of swarm has altered dramatically. No longer does the cluster (pool of resources) emulate a virtual docker host, and no longer can you run standard docker engine commands against the swarm cluster, you now need to use specific commands (service create, service inspect, service ps, service ls, service scale etc). If you run Docker engine commands (docker ps) what is returned is a list of containers running on the Docker Swarm Master HOST (not the cluster). If you want to interact with containers that make up a swarm “service”, you need to take multiple steps (service ps, to show the containers, and which host they are on, then change the focus of your docker commands to that host, connect to that host, and then issue the docker commands to manage the containers on that specific host/swarm member). |
| | | | |
| − | <pre>
| + | The key point of SwarmMode is that it is an overlay engine for running SERVICES, not Containers. In fact, a service actually comprises a number of tasks, with a task being a container and any commands to execute within the container (but a task might also be a VM in the future). |
| − | -A POSTROUTING -s 192.168.123.0/24 -d 224.0.0.0/24 -j RETURN
| |
| − | -A POSTROUTING -s 192.168.123.0/24 -d 255.255.255.255/32 -j RETURN
| |
| − | -A POSTROUTING -s 192.168.123.0/24 ! -d 192.168.123.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535
| |
| − | -A POSTROUTING -s 192.168.123.0/24 ! -d 192.168.123.0/24 -p udp -j MASQUERADE --to-ports 1024-65535
| |
| − | -A POSTROUTING -s 192.168.123.0/24 ! -d 192.168.123.0/24 -j MASQUERADE
| |
| − | </pre>
| |
| | | | |
| − | <pre>
| + | One of the major enhancements in Swarm mode is the load balancing, which is now built-in; now when you publish service, exposed ports will automatically be load balanced across the containers (tasks though, remember) that comprise that service. You don’t need to configure any additional load balancing. This change makes it incredibly easy to, say for instance, scale a nginx service from 1 worker task (container) to 10. |
| − | -A INPUT -i virbr1 -p udp -m udp --dport 53 -j ACCEPT | |
| − | -A INPUT -i virbr1 -p tcp -m tcp --dport 53 -j ACCEPT
| |
| − | -A INPUT -i virbr1 -p udp -m udp --dport 67 -j ACCEPT
| |
| − | -A INPUT -i virbr1 -p tcp -m tcp --dport 67 -j ACCEPT
| |
| − | -A INPUT -i virbrDocker -p udp -m udp --dport 53 -j ACCEPT
| |
| − | -A INPUT -i virbrDocker -p tcp -m tcp --dport 53 -j ACCEPT
| |
| − | -A INPUT -i virbrDocker -p udp -m udp --dport 67 -j ACCEPT
| |
| − | -A INPUT -i virbrDocker -p tcp -m tcp --dport 67 -j ACCEPT
| |
| − | </pre>
| |
| | | | |
| − | <pre>
| + | So, if you are using Swarm mode in Docker 1.12, you need to stop thinking about Containers (and trying to interact with the containers that make up a service) and rather, manage the service and tasks. |
| − | -A OUTPUT -o virbr1 -p udp -m udp --dport 68 -j ACCEPT
| |
| − | -A OUTPUT -o virbrDocker -p udp -m udp --dport 68 -j ACCEPT
| |
| − | </pre>
| |
| | | | |
| − | <pre>
| + | In Portainer.io, we exhibit the same behaviour as above, so if you click on “containers” you will only see the container |
| − | -A FORWARD -i virbr1 -o virbr1 -j ACCEPT
| |
| − | -A FORWARD -o virbr1 -j REJECT --reject-with icmp-port-unreachable
| |
| − | -A FORWARD -i virbr1 -j REJECT --reject-with icmp-port-unreachable
| |
| − | -A FORWARD -d 192.168.123.0/24 -o virbrDocker -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
| |
| − | -A FORWARD -s 192.168.123.0/24 -i virbrDocker -j ACCEPT
| |
| − | -A FORWARD -i virbrDocker -o virbrDocker -j ACCEPT
| |
| − | -A FORWARD -o virbrDocker -j REJECT --reject-with icmp-port-unreachable
| |
| − | -A FORWARD -i virbrDocker -j REJECT --reject-with icmp-port-unreachable
| |
| − | </pre>
| |
vim /etc/default/grub
2- Add Line below in GRUB_CMDLINE_LINUX systemd.unified_cgroup_hierarchy=0
Docker has been innovating at quite a dramatic pace, and focussing on making their technology easier to deploy, and applicable for a wider range of use cases. One of the features that has received the highest level of focus is Clustering/Orchestration. In Docker language, that means Swarm.
Prior to Docker 1.12 Swarm (Classic) existed as a standalone product, it relied on a complicated setup of external service discovery systems (eg consul) and a dedicated set of containers which ran as the swarm controllers. Load balancing network traffic across containers required external load balancers, and these needed to be integrated with service discovery to function correctly. Standalone Docker hosts were members of a swarm cluster, and the swarm controllers presented the pooled capacity from all hosts as a single “virtual” docker host. By presenting the swarm cluster as a virtual docker host meant that the way you interacted with Swarm was exactly the same way you interacted with a standalone host (docker run, docker ps, docker images, docker volumes), you just directed the commands (using –H=tcp://) at the swarm master IP:Port instead of individual swarm nodes.
A Docker 1.12-es verziója előtt a Swarm (Classic) egy külön álló termék volt, nem volt része a docker engine-nek. A swarm-ot a docker engine-en futó swarm konténerekkel kellett létrehozni. Vo
Since releasing Docker 1.12, and embedding Swarm Mode (I really wish they had called it something else to minimise confusion) into the core Docker engine, the functionality and management of swarm has altered dramatically. No longer does the cluster (pool of resources) emulate a virtual docker host, and no longer can you run standard docker engine commands against the swarm cluster, you now need to use specific commands (service create, service inspect, service ps, service ls, service scale etc). If you run Docker engine commands (docker ps) what is returned is a list of containers running on the Docker Swarm Master HOST (not the cluster). If you want to interact with containers that make up a swarm “service”, you need to take multiple steps (service ps, to show the containers, and which host they are on, then change the focus of your docker commands to that host, connect to that host, and then issue the docker commands to manage the containers on that specific host/swarm member).
The key point of SwarmMode is that it is an overlay engine for running SERVICES, not Containers. In fact, a service actually comprises a number of tasks, with a task being a container and any commands to execute within the container (but a task might also be a VM in the future).
One of the major enhancements in Swarm mode is the load balancing, which is now built-in; now when you publish service, exposed ports will automatically be load balanced across the containers (tasks though, remember) that comprise that service. You don’t need to configure any additional load balancing. This change makes it incredibly easy to, say for instance, scale a nginx service from 1 worker task (container) to 10.
So, if you are using Swarm mode in Docker 1.12, you need to stop thinking about Containers (and trying to interact with the containers that make up a service) and rather, manage the service and tasks.
In Portainer.io, we exhibit the same behaviour as above, so if you click on “containers” you will only see the container
