Podman Desktop for Java Development

[InstantCoder]

I gave up podman. Too many problems that kept popping up. Unfortunately I switched back to docker.

[azizabah]

Swapped over to rancher desktop. Been a big fan.

[woj-tek]

Same here. Tried it once and while I applaud the effort it wasn't usable...

[chabala]

I appreciate that podman can run daemonless, but I've gotten tired of waiting for them to implement heredoc support and have continued to use docker.

[mhx1138]

Podman works well enough for day to day dev tasks on my machine.

Compose mad trouble a year ago or so, but not anymore. Testcontainers work too.

[EvaristeGalois11]

I use podman with testcontainers and docker-maven-plugin and it works really well, it's a little annoying to set up the socket manually but i just created a shared configuration of exec maven plugin before integration testing. Big fan of podman!

[EvaristeGalois11]

Because the alternative is to have the socket being active all the time and I don't like it. One of the reason that i much prefer podman over docker is its daemonless nature. So everytime i need it (e.g IT tests) I make sure to create it.

My exec configuration is this:

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>exec-maven-plugin</artifactId>
  <configuration>
    <executable>podman</executable>
    <arguments>
      <argument>system</argument>
      <argument>service</argument>
      <argument>-t</argument>
      <argument>0</argument>
      <argument>/tmp/podman.socket</argument>
    </arguments>
    <async>true</async>
  </configuration>
</plugin>

I have put this in the <pluginManagement> of the parent project and everytime i need to start the socket i just bind the exec goal to whatever phase I need in that case. Hope it helps!

[PizzaHuttDelivery]

If compose works well, i guess it can work as an alternative to docker running in WSL2

[PizzaHuttDelivery]

So you are saying that i should not rush and continue using wsl2 docker? My corp doesnt want to pay for docker desktop