Menu
I started couchbase community with docker as following:
docker run -e CB_RAMSIZE=256 -e "CB_ADMIN_PWD=123456" --name couchbase-community -p 8091-8094:8091-8094 -p 11210:11210 crobin/couchbase-community
I'm now trying to stop it with
docker stop couchbase-community
docker kill couchbase-community
docker kill -s 9 couchbase-community
Nothing stops it.
It's just stuck alive. Anyway for me to stop that container?!
the result of docker ps -a
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9deed40a7db9 crobin/couchbase-community "bash /bin/start-cb.…" 32 hours ago Up 32 hours (healthy) 0.0.0.0:8091-8094->8091-8094/tcp, 11207/tcp, 11211/tcp, 0.0.0.0:11210->11210/tcp, 18091-18094/tcp couchbase-community
7b265619e593 nginx "--name nginx" 8 weeks ago Created 80/tcp laughing_brahmagupta
65f7ebdf03ba nginx "1000" 8 weeks ago Created 80/tcp lucid_heyrovsky
e402edffeeaa db148b62d457 "tini -- start-noteb…" 2 months ago Created admiring_brattain
60e58a104b52 db148b62d457 "tini -- start-noteb…" 2 months ago Created eloquent_elion
a668f900566e db148b62d457 "tini -- start-noteb…" 2 months ago Created unruffled_poitras
6fe2e4bd18bc jupyterhub/jupyterhub "--generate-config" 2 months ago Created 8000/tcp
docker and OS version
docker Version 17.12.0-ce-mac55 (23011) on macbook 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
981
docker rm -f The final option for stopping a running container is to use the --force or -f flag in conjunction with the docker rm command. Typically, docker rm is used to remove an already stopped container, but the use of the -f flag will cause it to first issue a SIGKILL.
Stop YouTrack docker container For a graceful shutdown, you can also use the standard ` docker kill --signal=SIGTERM <containerId> ` command.
When you start Docker this way, it runs in the foreground and sends its logs directly to your terminal. To stop Docker when you have started it manually, issue a Ctrl+C in your terminal.
Simply run your application through the Couchbase Server SDK of your choice on the host, and point it to http://localhost:8091/pools to connect to the container. For running a sample application, refer to the Sample Application guide. Official Couchbase Server images on Docker Hub are based on the latest supported version of Ubuntu.
This command will only display the status for couchbase1 container. Run docker ps without the filter, to display all running containers on the system. There is another way to check the status/state of the container and that's with docker inspect .
First, open your terminal and install these tools, used by some of the core Couchbase Server packages. Download and install the .deb meta-package, it contains the necessary information for apt to retrieve Couchbase’s necessary packages and public signing keys. Now you are ready to install the Couchbase Server CE latest release.
You can now use the navigation tab icon on the top right corner of your desktop to manage your server. For a more extensive install guide, you can follow the Couchbase documentation for macOS.
This looks like your docker daemon is stuck or this specific container/something broke it.
Firstly if you restart your docker demon/Docker for Mac (using its panel) container will be stopped regardless, as engine that runs on it will go down.
Then either, if you do not care about it's data stored in volume you can just remove it via docker rm -f 9deed40a7db9 , or just restart it.
I would reccomend doing docker system prune && docker volume prune if you do not care about volumes/unused images/containers you have on your machine and to check what image you using does in its Dockerfile and what volumes it introduces to the docker engine.
64
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
