Docker container save logs on the host directory

Question

I have a question similar to this one. When run my docker-compose.yml file, I automatically create a docker image and as specified in my dockerfile, I run certain apps. These apps produce some logs, but these logs are written inside the docker container, in /home/logs/ folder.

How can I indicate that these logs be writted outside the container, on my /path/on/host address? Simply because if the container was failed, I need to see the logs and not lose them!

This is my docker-compose.yml:

version: '3'
services:
  myapp:
    build: .
    image: myapp
    ports:
      - "9001:9001"

and here is my dockerfile:

FROM java:latest
COPY myapp-1.0.jar /home
CMD java -jar /home/myapp-1.0.jar

And I simply run it on production machine with docker-compose up -d.

(BTW, I'm new to dockers. Are all of my steps correct? Am I missing anything?! I see all is fine and myapp is running though!)

Nebri · Accepted Answer · 2019-01-26T03:06:24.830

All you need is a docker volume in order to persist the log files. So in the same directory as your docker-compose.yml create a logs directory, then define a volume mount. When defining a mount remember the syntax is <host_machine_directy>:<container_directory>.

Give the following volume a try and let me know what you get back.

version: '3'
services:
  myapp:
    build: .
    image: myapp
    ports:
      - "9001:9001"
    volumes:
      - ./logs:/home/logs

Also worth noting that persistence goes both ways with this approach. Any changes made to the files from within the container are reflected back onto the host. Any changes from the host, are also reflected inside the container.

Hi. I tried using `volumes`. When running the docker, I see `/logs` folder on host. But for some reason nothing inside. `Unable to create file logs/processor.log java.io.IOException: Could not create directory /home/logs` — Tina J, Feb 06 '19 at 21:07

Ijaz Ahmad · Answer 2 · 2019-01-27T23:30:40.517

Yes , you can mount the volume from host into the container as outlined in the above answer , using a bind mount
In production , I would highly recommend sending logs of all containers to some central location , so that even if the whole docker host goes down you still have access to logs and maybe can easily analyse , filter, set watchers on log errors and make a dashboard , such as ELK

https://docs.docker.com/config/containers/logging/configure/

For this to work , you need to configure the app to send logs to stdout instead , and then configure docker daemon to send logs to one of your end points such as logstash , then you can configure logstash to do some pre-processing ( if needed ) and then stream it to your elasticsearch instance.

Going one step further , you may consider a container management system such as kubernetes with central logging to ELK and metering to promethous.

Docker container save logs on the host directory

2 Answers2

Linked