I'm experiencing something that looks like regression to KARAF-5332. I've prepared scripts for liveness / readiness probe for Kubernetes, that are using $KARAF_HOME/bin/status.
To test them, I've started docker container locally (with docker run) and when calling /bin/status I'm getting the error: karaf@15392c7dffa3:/opt/karaf$ bin/status status: Ignoring predefined value for KARAF_HOME ERROR: transport error 202: bind failed: Address already in use ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750] However, when I've started the same container in the cluster, I'm getting no exception. This is really the same container. In both cases I use the tagged image from local docker repository. The build details: I'm using the newest Karaf (4.2.8). Docker version: 19.03.6 Java version: /usr/lib/jvm/java-8-openjdk-amd64 Java params: -Xmx1G -Xdebug -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 Docker has following port redirections: 5005/tcp 0.0.0.0:5205 8080/tcp 0.0.0.0:8280 Does bin/status make some assumption about which ports are free? Because there are a few services that are running on the same machine (however, on the other machine, I can replicate the same behaviour). -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
