# Docker Logs keep getting dropped with tried to parse field \[image\] as object, but found a concrete value error **URL:** 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 **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:** 36
### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb) #### Post date: [March 6, 2023, 2:47am 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/36 "2023-03-06T02:47:36Z")
@jerrac **I have a super simple workaround !!! It Works ...** I will still work behind the scenes to get this fixed So in the docker integration Under Container Logs -\> Advanced Setting Processors I added this ```auto - rename: fields: - from: "container.image" to: "container.image.name" ignore_missing: true fail_on_error: false ``` ![Screen Shot 2023-03-05 at 6.44.10 PM](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c8e9d17fe7e07e677b708ed603cdc97911bf7c3.png) ![Screen Shot 2023-03-05 at 6.50.29 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/d/3d4e64ad0f36b8f59b6cf2ff2f96cc45a3750bff.png) The processors renames the field _ **before** _ it is sent to elastic and now here are the Fixed Logs 🙂 ![Screen Shot 2023-03-05 at 6.44.27 PM](https://us1.discourse-cdn.com/elastic/original/3X/8/3/8380386efc8987cd203be7de15aa43379a20274d.png) --- _[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)._