@RomanS - very interesting. I’ve shared this with our distribution team to see if they have any thoughts on what might be happening between environments. In a perfect world, it works the same everywhere with containers!
What version of Docker is on your Linux workstation? Do you know if your company enforced a private container registry?
The images should be the same across all environments and I’ve not experienced something like this, so I’m hoping some of our engineers can provide some insight!
@nathan.loding yes, in containers world all should be fine.
The only one step in our whole flow that is outside containers is our packaged JAR. We package it locally, using local mvn/java.
Also I know that workstation has no internet access, in it’s normal way, only some allowed things, like mvn repos, dockerhub etc. Could it be that camunda tries to make some outgoing call somewhere?
Depending on the access the remote machine has, is there a way to upload a JAR from your Mac to it for testing? Alternately, could the compiled JAR from the remote machine be retrieved somehow for testing?
There shouldn’t be any outbound/non-local calls in this particular setup.
@nathan.loding yes I was thinking about passing JAR somehow to that machine, but that is not possible (or almost not possible ) and I am pretty sure not allowed. Let’s park our discussion here as we know this is not something that I missed in Camunda itself.
Java 21.0.6, maven 3.9.2. This is not the problem 99.99%. My feeling.
) and I am pretty sure not allowed. Let’s park our discussion here as we know this is not something that I missed in Camunda itself.