Martin

The `build` block of `docker_registry_image` is now deprecated and will be removed with the next major version. Please migrate to using the `build` block of the `docker_image`. There were many...

The `build` block of `docker_registry_image` is now deprecated and will be removed with the next major version. Please migrate to using the `build` block of the `docker_image`. There were many...

I just tested this on my local machine. I have two `docker_image` resources, one builds for `linux/amd64` and one builds for `linux/arm64`. Both images where build and work on their...

I would consider this issue as outdated. Hashicorp has released its new SDK (called plugin framework) 3 weeks ago: https://github.com/hashicorp/terraform-plugin-framework It has some features which would come in handy for...

To be honest, I still don't fully understand your problem regarding watchtower, but I still did some digging and research. When running `docker run --name nginx_test -d nginx:1.23` and `docker...

Closing this. We have improved the error logging in the past months and, as @suzuki-shunsuke pointed out, we cannot easily access the logs of the docker client itself (especially when...

This issue is over 2 years old. In addition to that, Hashicorp released a new Terraform provider SDK (called terraform-plugin-framework) which we will eventually migrate to, as it offers some...

We are always trying to re-use as much code from `docker/cli` or `moby/moby`. The challenge is, that our interface is a lot different to the one of the `docker` cli....

The `build` block of `docker_registry_image` is now deprecated and will be removed with the next major version. Please migrate to using the `build` block of the `docker_image`. There were many...

We are currently reading the ports data from the `container.NetworkSettings.Ports`, which is `{}` when the container has exited. However, we can get the full port information from `HostConfig.PortBindings`, but we...