Roland Huß

@rhatdan docker-maven-plugin has two major parts: * _Building container images_ by using Docker REST API directly from the the plugin. Abstracting that build part has been started in #1116 but...

> However, if you use the API directly, that obviously won't help. That's the point, this plugin does not user the `docker` cli but talks directory with the Docker daemon...

As an idea, we could add support for starting (and stopping) the Podman service transparently, similar like the support we have for docker-machine (see the docs).

Looks like a mismatch in the content-type when uploading the build context to the daemon. Should be easy to fix (assuming that Docker also works with `x-tar` as content type)....

I see, thanks for the investigation. Let's tackle Podman support for the next release. At least those two issues should be easy to fix.

For `docker:tag` --> https://dmp.fabric8.io/#docker:tag For `docker:pull` : Why would you need that ? The plugin creates container images, it's not a general docker manipulation tool. You still can use `docker...

> We're now at Java 8 EOL. Java 17 is the current LTS. I recommend moving to Java 11. True, but there are still surprisingly many people using Java 8...

Java 8 already has container support since u191 (https://blog.softwaremill.com/docker-support-in-new-java-8-finally-fd595df0ca54). For even older versions, there a startup scripts like https://github.com/fabric8io-images/run-java-sh that help set the proper memory boundaries. I agree (and also...

That would be interesting but requires quite some effort: A service that needs to be highly available for receiving the data. The user to opt-in for sending the data (i...

This is currently not possible and there are no plans to implement this, but if someone wants to pick this up, it should be possible to integrate as it looks...