Docker Compose “Ghost Containers”How is Docker different from a virtual machine?Should I use Vagrant or Docker for creating an isolated environment?How to list containers in DockerHow to get a Docker container's IP address from the host?How to remove old Docker containersHow to deal with persistent storage (e.g. databases) in DockerCopying files from Docker container to hostCopying files from host to Docker containerHow to copy Docker images from one host to another without using a repositoryFrom inside of a Docker container, how do I connect to the localhost of the machine?
copy and scale one figure (wheel)
When were female captains banned from Starfleet?
Is there a working SACD iso player for Ubuntu?
How much character growth crosses the line into breaking the character
Fear of getting stuck on one programming language / technology that is not used in my country
What is this called? Old film camera viewer?
Problem with TransformedDistribution
Can I sign legal documents with a smiley face?
Is it possible to have a strip of cold climate in the middle of a planet?
How do I color the graph in datavisualization?
Is it possible to put a rectangle as background in the author section?
Is there any references on the tensor product of presentable (1-)categories?
If infinitesimal transformations commute why dont the generators of the Lorentz group commute?
What should you do if you miss a job interview (deliberately)?
On a tidally locked planet, would time be quantized?
Multiplicative persistence
2.8 Why are collections grayed out? How can I open them?
Strong empirical falsification of quantum mechanics based on vacuum energy density
Electoral considerations aside, what are potential benefits, for the US, of policy changes proposed by the tweet recognizing Golan annexation?
The screen of my macbook suddenly broken down how can I do to recover
Melting point of aspirin, contradicting sources
Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?
Why should universal income be universal?
Delivering sarcasm
Docker Compose “Ghost Containers”
How is Docker different from a virtual machine?Should I use Vagrant or Docker for creating an isolated environment?How to list containers in DockerHow to get a Docker container's IP address from the host?How to remove old Docker containersHow to deal with persistent storage (e.g. databases) in DockerCopying files from Docker container to hostCopying files from host to Docker containerHow to copy Docker images from one host to another without using a repositoryFrom inside of a Docker container, how do I connect to the localhost of the machine?
I am using docker-compose to deploy an application combining a number of different images.
Using Docker version 18.09.2, build 6247962
Docker-compose 1.117
Primarily, I have
- ZooKeeper
- Kafka
- MYSQLDb
I notice a strange problem where i could not start my application with docker-compose up due to port already being assigned. I then checked docker stats and saw that there were three containers named "test_ZooKeeper.1slehgaior"
"test_Kafka.kgjdorgsr"
"test_MYSQLDB.kgjdorgsr"
I have tried kill the containers, removing them and pruning the system. When ever I kill one of these containers, it instantly restarts and I cannot for the life of me determine where they are being created from!
Please help :)
docker docker-compose
New contributor
add a comment |
I am using docker-compose to deploy an application combining a number of different images.
Using Docker version 18.09.2, build 6247962
Docker-compose 1.117
Primarily, I have
- ZooKeeper
- Kafka
- MYSQLDb
I notice a strange problem where i could not start my application with docker-compose up due to port already being assigned. I then checked docker stats and saw that there were three containers named "test_ZooKeeper.1slehgaior"
"test_Kafka.kgjdorgsr"
"test_MYSQLDB.kgjdorgsr"
I have tried kill the containers, removing them and pruning the system. When ever I kill one of these containers, it instantly restarts and I cannot for the life of me determine where they are being created from!
Please help :)
docker docker-compose
New contributor
add a comment |
I am using docker-compose to deploy an application combining a number of different images.
Using Docker version 18.09.2, build 6247962
Docker-compose 1.117
Primarily, I have
- ZooKeeper
- Kafka
- MYSQLDb
I notice a strange problem where i could not start my application with docker-compose up due to port already being assigned. I then checked docker stats and saw that there were three containers named "test_ZooKeeper.1slehgaior"
"test_Kafka.kgjdorgsr"
"test_MYSQLDB.kgjdorgsr"
I have tried kill the containers, removing them and pruning the system. When ever I kill one of these containers, it instantly restarts and I cannot for the life of me determine where they are being created from!
Please help :)
docker docker-compose
New contributor
I am using docker-compose to deploy an application combining a number of different images.
Using Docker version 18.09.2, build 6247962
Docker-compose 1.117
Primarily, I have
- ZooKeeper
- Kafka
- MYSQLDb
I notice a strange problem where i could not start my application with docker-compose up due to port already being assigned. I then checked docker stats and saw that there were three containers named "test_ZooKeeper.1slehgaior"
"test_Kafka.kgjdorgsr"
"test_MYSQLDB.kgjdorgsr"
I have tried kill the containers, removing them and pruning the system. When ever I kill one of these containers, it instantly restarts and I cannot for the life of me determine where they are being created from!
Please help :)
docker docker-compose
docker docker-compose
New contributor
New contributor
New contributor
asked 2 days ago
Tom RaeTom Rae
31
31
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you look into your docker-compose.yaml I'm pretty sure you'll find a restart:always
somewhere. If you want to correctly shut down a running docker container managed by docker-compose, one way is to use docker-compose down
from the directory where your yaml sits.
More information on the subject:
https://docs.docker.com/config/containers/start-containers-automatically/
Otherwise, you might try out to stop a single running container instead of killing it, which according to my memory tells docker not to restart it again, while a killed container looks to the service like it just has crashed. Not too sure about the last part though.
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Tom Rae is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55281433%2fdocker-compose-ghost-containers%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you look into your docker-compose.yaml I'm pretty sure you'll find a restart:always
somewhere. If you want to correctly shut down a running docker container managed by docker-compose, one way is to use docker-compose down
from the directory where your yaml sits.
More information on the subject:
https://docs.docker.com/config/containers/start-containers-automatically/
Otherwise, you might try out to stop a single running container instead of killing it, which according to my memory tells docker not to restart it again, while a killed container looks to the service like it just has crashed. Not too sure about the last part though.
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
add a comment |
If you look into your docker-compose.yaml I'm pretty sure you'll find a restart:always
somewhere. If you want to correctly shut down a running docker container managed by docker-compose, one way is to use docker-compose down
from the directory where your yaml sits.
More information on the subject:
https://docs.docker.com/config/containers/start-containers-automatically/
Otherwise, you might try out to stop a single running container instead of killing it, which according to my memory tells docker not to restart it again, while a killed container looks to the service like it just has crashed. Not too sure about the last part though.
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
add a comment |
If you look into your docker-compose.yaml I'm pretty sure you'll find a restart:always
somewhere. If you want to correctly shut down a running docker container managed by docker-compose, one way is to use docker-compose down
from the directory where your yaml sits.
More information on the subject:
https://docs.docker.com/config/containers/start-containers-automatically/
Otherwise, you might try out to stop a single running container instead of killing it, which according to my memory tells docker not to restart it again, while a killed container looks to the service like it just has crashed. Not too sure about the last part though.
If you look into your docker-compose.yaml I'm pretty sure you'll find a restart:always
somewhere. If you want to correctly shut down a running docker container managed by docker-compose, one way is to use docker-compose down
from the directory where your yaml sits.
More information on the subject:
https://docs.docker.com/config/containers/start-containers-automatically/
Otherwise, you might try out to stop a single running container instead of killing it, which according to my memory tells docker not to restart it again, while a killed container looks to the service like it just has crashed. Not too sure about the last part though.
answered 2 days ago
AarkonAarkon
358
358
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
add a comment |
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
1
1
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
Hi Aarkon, Thanks for the heads up! I realised what i had done was start a stack using docker stack deploy rather than deploying through docker compose up. I had then moved the directories and this threw me off the scent!
– Tom Rae
2 days ago
add a comment |
Tom Rae is a new contributor. Be nice, and check out our Code of Conduct.
Tom Rae is a new contributor. Be nice, and check out our Code of Conduct.
Tom Rae is a new contributor. Be nice, and check out our Code of Conduct.
Tom Rae is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55281433%2fdocker-compose-ghost-containers%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown