Benjamin Muschko

Was the second command meant to be a Gradle command? `docker logContainer | tee test.txt`. Be aware that the task has a field named `sink` for writing the output to...

I actually see multiple concerns here: 1. Bug: Extra new lines 2. Feature request: Being able to write to standard output while at the same time writing to a file...

Feel free to open a separate issue and change the issue description here. Heads up: I do not have to time to work on it but maybe someone else in...

You mean the Javadoc for the `Dockerfile` task? https://bmuschko.github.io/gradle-docker-plugin/current/api/com/bmuschko/gradle/docker/tasks/image/Dockerfile.html IMHO, it's well enough documented there. Also, side not if that's not clear: You don't have to use this task. You...

> Why not at least link to that in the user guide where it discusses Dockerfile examples and say this is where all the directives are documented. The custom tasks...

The Docker remote API does not support buildkit as of now.

We are not using the Docker executable with this plugin. We are using the [RESTful API](https://docs.docker.com/reference/api/engine/).

OK, seems like Docker added that to the API recently. Unfortunately, Docker Java, the wrapper around the Docker API, does not support it yet: https://github.com/docker-java/docker-java/pull/2362

I don't fully understand your situation. If a dependency in this plugin was relocated, then it should not have an effect on other plugins that use the same dependency in...

What I am saying here is that the real solution would be separate classloaders for plugins classpaths in Gradle itself which would not require relocating packages and clashes between dependencies...