Gain insights into Docker Compose, Docker Swarm, and Docker Networking. Explore app deployment, multi-container management, and security tools to thrive in the cloud-first environment.

Dockerfile2.tar.gz

counter-app2

counter-app-manual

counter-app-automatic

counter-app-automatic-up-d

port mapping

ingress_load_balancing

basic_shell

sharing_storage

counter-app2-copy

If you want to thrive in the modern cloud-first world, you need to know Docker. But don’t stress, this course will give you all the skills you need.

To kick things off, you will learn how to deploy apps with Docker Compose, a key tool for managing multi-container applications running in single-engine mode. You will then move onto Docker Swarm which will allow you to stand up containers and orchestrate them at scale.

Towards the back half of the course, you will take a deep dive into Docker Networking, deploying apps with Docker Stacks, and some of the industry tools used for keeping Docker secure.

By the end of this course, you will be equipped with the knowledge and tools to run Docker at scale, no matter how many containers you have.

Docker Deep Dive: Advanced Techniques

## docker service logs
Swarm Service logs can be viewed with the `docker service logs` command. However, not all logging drivers support the command.

By default, Docker nodes configure services to use the `json-file` log driver, but other drivers exist, including:

- `journald` (only works on Linux hosts running `systemd`)
- `syslog`
- `splunk`
- `gelf`

`json-file` and `journald` are the easiest to configure, and both work with the `docker service logs` command. The format of the command is `docker service logs <service-name>`.

If you're using 3rd-party logging drivers you should view those logs using the logging platform's native tools.

The following snippet from a `daemon.json` configuration file shows a Docker host configured to use `syslog`.

# docker service logs
Swarm Service logs can be viewed with the `docker service logs` command. However, not all logging drivers support the command.

By default, Docker nodes configure services to use the `json-file` log driver, but other drivers exist, including:

- `journald` (only works on Linux hosts running `systemd`)
- `syslog`
- `splunk`
- `gelf`

`json-file` and `journald` are the easiest to configure, and both work with the `docker service logs` command. The format of the command is `docker service logs <service-name>`.

If you're using 3rd-party logging drivers you should view those logs using the logging platform's native tools.

The following snippet from a `daemon.json` configuration file shows a Docker host configured to use `syslog`.

Let’s learn to troubleshoot a swarm service using its logs.

About the Course

Multi-container Apps with Compose

Docker Swarm

Docker Networking

Docker Overlay Networking

Volumes and Persistent Data

Deploying Applications with Docker Stacks

Security in Docker

What Next

Appendix: Getting Docker and Compose

Troubleshooting

docker service logs