And then ran:
bash-4.2$ cd /var/log/
bash-4.2$ pwd
/var/log
bash-4.2$ ls
btmp grubby_prune_debug lastlog tallylog wtmp yum.log
bash-4.2$ cd
bash-4.2$ ls
LICENSE.txt NOTICE.txt README.md apm-server apm-server.yml data fields.yml ingest kibana logs
bash-4.2$ cd logs/
bash-4.2$ ls
bash-4.2$
docker run -it docker.elastic.co/apm/apm-server:6.7.0 /bin/bash
you override container start script, and the apm server never starts, hence no logging appearing
try running the container first
docker run -d -it --name apm docker.elastic.co/apm/apm-server:6.7.0
and then connecting to it, to see if you find those logs
docker exec -it apm bash
EDIT: also docker image does not log to files by default, you can get the logs by running docker container logs apm based on the above example. If you still want to log to files, you will have to either override the config or build a custom image
what specifically should I add so it overrides the config? my understanding was that apm-server by default logs to /var/log. this is what it did when I ran it in the vm
EDIT: you are saying that this same default logging of apm-server to /var/log does not apply to the container I guess?
What I will do is custom configure it to log in a specific directory of the container and work with that. I will overtly put in the config to log to var/log
Either that or I will look at ways to turn docker logs to log to the VM. that would be the second option
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.