# APM agent detects my system as a container? **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [August 10, 2020, 8:35am UTC](https://discuss.elastic.co/t/apm-agent-detects-my-system-as-a-container/244369 "2020-08-10T08:35:43Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jsec](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@jsec](https://discuss.elastic.co/u/jsec)\ **Post date:** [August 10, 2020, 8:35am UTC](https://discuss.elastic.co/t/apm-agent-detects-my-system-as-a-container/244369/1 "2020-08-10T08:35:43Z")
If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂 TIP 1: select at least one tag that further categorizes your topic. For example `server` for APM Server related questions, `java` for questions regarding the Elastic APM Java agent, or `ui` for questions about the APM App within Kibana. TIP 2: Check out the [troubleshooting guide](https://www.elastic.co/guide/en/apm/get-started/current/troubleshooting.html) first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you. **Kibana version** : 7.1.1 **Elasticsearch version** : 7.1.1 **APM Server version** : 7.1.1 **APM Agent language and version** : elastic-apm-agent-1.18.0.RC1.jar **Browser version** : Chrome 84.0.4147.89 **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: rpm install **Fresh install or upgraded from other version?** fresh **Is there anything special in your setup?** No **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: started my java application with tomcat shows unexpected info in the log file catalina.out **Steps to reproduce** : 1. Modify the setenv.sh file to contain the agent parameters 2. Start the service 3. Check the logs **Errors in browser console (if relevant)**: no **Provide logs and/or server output (if relevant)**: My setenv.sh is configured as follows: > CATALINA\_OPTS="$CATALINA\_OPTS -javaagent:/opt/app/environment/liferay/runtime/tomcat-9.0.33/elastic-apm-agent-1.18.0.RC1.jar -Delastic.apm.service\_name=liferay -Delastic.apm.application\_packages=com.liferay,com.es -Delastic.apm.server\_urls=[http://192.168.1.2:8200](http://192.168.1.2:8200) -Delastic.apm.log\_level=DEBUG -Delastic.apm.log\_file=/opt/app/environment/liferay/runtime/tomcat-9.0.33/logs/agent.log" Starting the application outputs the following: > 2020-08-05 09:31:47,920 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 11:pids:/ > 2020-08-05 09:31:47,922 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 10:hugetlb:/ > 2020-08-05 09:31:47,923 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 9:cpuset:/ > 2020-08-05 09:31:47,923 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 8:memory:/ > 2020-08-05 09:31:47,924 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 7:freezer:/ > 2020-08-05 09:31:47,924 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 6:devices:/ > 2020-08-05 09:31:47,925 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 5:net\_prio,net\_cls:/ > 2020-08-05 09:31:47,926 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 4:blkio:/ > 2020-08-05 09:31:47,926 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 3:perf\_event:/ > 2020-08-05 09:31:47,927 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 2:cpuacct,cpu:/ > 2020-08-05 09:31:47,928 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 1:name=systemd:/user.slice/user-0.slice/session-3605.scope > 2020-08-05 09:31:47,929 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - container ID is null Does the agent detects that is running inside a container like Kubernetes? Cause it's not. It's a CentOS 7.8 VM server. The app is working, and the restults from the agent are visible under Kibana, however, I don't understand why it outputs the log above. Thanks! Catalin ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 31, 2020, 4:35am UTC](https://discuss.elastic.co/t/apm-agent-detects-my-system-as-a-container/244369/2 "2020-08-31T04:35:50Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.