There is no need to do this. Just connect Jenkins to the host, then delete the container and run a new one. If the deployment is simple, just update the directory mounted with -v and restart the container.
You can use the container name to access the container service from another one under the same bridge network, not the IP address of the container! IP may change
There is no need to do this. Just connect Jenkins to the host, then delete the container and run a new one. If the deployment is simple, just update the directory mounted with -v and restart the container.
You can use the container name to access the container service from another one under the same bridge network, not the IP address of the container! IP may change