Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Inconsistent usage of "docker-compose up" with and without "-d" option
See original GitHub issueIssue Description
KT should have consistent usage of either “docker-compose up” or “docker-compose up-d”, but right now it is a mix:
[16:14:34] ~/git/kafka-tutorials(master) ✗: grep -ir "docker-compose up" _includes/* | grep "up -d" | wc -l
28
[16:14:38] ~/git/kafka-tutorials(master) ✗: grep -ir "docker-compose up" _includes/* | grep -v "up -d" | wc -l
14
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
docker compose up - Docker Documentation
The docker compose up command aggregates the output of each container (like docker compose logs --follow does). When the command exits, all containers...
Read more >docker-compose up -d doesn't expose ports when defined ...
docker -compose up -d is supposed to expose the ports and supposedly be able to publish the ports according to the yml, however,...
Read more >docker-compose for Detached mode - Stack Overflow
Options : -d, --detach Detached mode: Run containers in the background, print new container names. Incompatible with --abort-on-container-exit.
Read more >Examples of docker-compose up | Advantages - eduCBA
This is a guide to docker-compose up. Here we discuss the introduction to docker-compose up, examples and advantages respectively.
Read more >docker-compose up
Options : -d, --detach Detached mode: Run containers in the background, print new container names. Incompatible with --abort-on-container-exit. --no-color ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, the decision was to move to daemon mode exclusively. I am not aware of a previous decision to switch away from daemon mode to non-daemon mode. The current state reflects a transition in progress to
-d.Related: #202 #383
@gAmUssA I think that discussion and switch happened before I joined the team. I only remember discussions that we should move to
docker-compose up -d, so I can’t add any context here.