Shutting Down the Peer Process in the Docker Container Shuts Down the Container

[btiller123]

As specified in the cli reference when using the 'peer node unjoin' command, the peer must be offline. However, the only way to set the peer to be offline is to kill the peer process. Killing this process causes the docker container in which it is running to stop as well. This stoppage occurs because the pid for 'peer node start' is 1.

There are several problems with stopping the docker container when the peer is stopped.

1. Pushing chaincode fails with Error: failed to retrieve endorser client for install: endorser client failed to connect to 172.26.123.170:7405: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.26.123.170:7405: connect: connection refused"

2. Since the container is stopped the externally run peer node commands fail.

3. The container shell cannot be accessed to run the peer node command from within the container.

Please fix so that stopping the peer process does not shutdown the docker container, and that chain code can still be pushed to existing peers.