# Docker Logs keep getting dropped with tried to parse field \[image\] as object, but found a concrete value error **URL:** \ **Category:** Elastic Agent\ **Created:** [February 23, 2023, 3:01am UTC](https://discuss.elastic.co/t/docker-logs-keep-getting-dropped-with-tried-to-parse-field-image-as-object-but-found-a-concrete-value-error/326245 "2023-02-23T03:01:16Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jerrac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerrac/32/52980_2.png) [@jerrac](https://discuss.elastic.co/u/jerrac)\ **Post date:** [February 24, 2023, 5:20pm UTC](https://discuss.elastic.co/t/docker-logs-keep-getting-dropped-with-tried-to-parse-field-image-as-object-but-found-a-concrete-value-error/326245/2 "2023-02-24T17:20:29Z")
I've found the same problem on my cluster at work. On that cluster I had a custom ingest pipeline set up, so I removed that. It didn't change anything. I double checked that I wasn't just filtering things out by accident by looking at the docker logs datastream index. For the one with the date 2023.02.22 on it, there are 0 docs. For the index from 2023.01.19, there are 6+ million docs. My work cluster is running 3 8.6.1 nodes on Ubuntu 18.04, The agents that are supposed to be grabbing docker logs are installed at the system level. Not in docker. Any ideas? Edit: [this](https://discuss.elastic.co/t/getting-illegal-state-exception-error-while-pushing-logs-to-elasticsearch/290029/2) sure sounds like my issue, but how in the world did a mapping get messed up when I have been letting Elastic Agent/Kibana/etc manage all that for me? --- _[View the full topic](https://discuss.elastic.co/t/docker-logs-keep-getting-dropped-with-tried-to-parse-field-image-as-object-but-found-a-concrete-value-error/326245)._