Closed kamigerami closed 8 years ago
@kamigerami I don't remember having this problem. Is your stdout get redirected? Could Vagrant change CLI environment?
@dongluochen - I do get the output if I use the -i flag. Not sure if vagrant actually does something however I'll try the CLI directly from virtualbox and report back.
I'll try it out with docker machine on my Mac (as the docs suggest) as well.
I'll even try it out on actual vmware hosts running swarm (and leave out vagrant altogether) just to make sure.
I can confirm that it works fine without the -i flag using only virtualbox or only vmware or only docker-machine on my local workstation (not using vagrant).
So when using vagrant the -i option might be needed.
Closing this.
Output of
docker version
:Swarm version 1.1.3
Additional environment details (AWS, VirtualBox, physical, etc.):
Vagrant / Virtualbox
Steps to reproduce the issue:
Describe the results you received:
No output thought the container runs fine and exits.
Describe the results you expected:
As in what the docs suggest
"4. Run a container on the Swarm." https://docs.docker.com/swarm/install-w-machine/
Additional information you deem important (e.g. issue happens only occasionally):
Update docs to provide the -i flag to the docker run command when using swarm so the -i flag allows us to make an interactive connection by grabbing the standard in (STDIN) of the container and outputing the "Hello from Docker"