Martin

Maintainer here: I am monitoring this issue closely and reading every comment. Under the hood we are simply using the `docker` client, so any issues from the docker client also...

Thanks for the issue! Due to limited availability we are currently focusing on issues which have been open for a long time and have many "upvotes". But it can very...

Thanks for the updates! I assume you are also using the `terraform-aws-modules/lambda/aws//modules/docker-build` module? Could you post your values for `source_path` and `docker_file_path`?

Ah, I just noticed something. The original post is about a inconsistent plan in `docker_registry_image`. Your error is about `docker_container`. Do you mind quickly making a new issue with "docker_container:...

@areed1192 Could you post your values for source_path and docker_file_path?

Thanks for submitting this issue! I am currently working on other issues, so this would take a while to fix. In general, we are planning on moving all the `docker...

This is actually tricky to implement for two reasons: 1. The https://github.com/docker/cli (where we often look at implementation details) has two different ways of implementing that: one for docker servers...

`docker logs` is only for running docker containers, it does not contain build logs for failed builds... One thing I could look into is passing the build error all the...

I have just tested it with a really simple Dockerfile ``` FROM busybox RUN ./build.sh ``` and the corresponding terraform ``` terraform { required_providers { docker = { source =...

@Vicar-of-AI, as already mentioned, it is sadly not possible to directly write build/upload progress to `stdout` (related terraform sdk issue: https://github.com/hashicorp/terraform-plugin-sdk/issues/145) The only possible way would be to output this...