Docker - swarm with docker toolbox doesn't run

Multi tool use
Multi tool use












0















i applied docker tutorial to set up a swarm.
I used docker toolbox, because i'm on windows 10 Family.



i step all statements, but at the end, the statement "curl ip_adress" doesn't run. error also with access on url.



$ docker --version
Docker version 18.03.0-ce, build 0520e24302


docker-compose.yml, located in /home/docker of virtual machine called "myvm1" :



version: "3"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
replicas: 5
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- "80:80"
networks:
- webnet
networks:
webnet:


swarm :



$ docker-machine ssh myvm1 "docker stack ps getstartedlab"
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
blmx8mldam52 getstartedlab_web.1 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
04ctl86chp6o getstartedlab_web.2 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
r3qyznllno9j getstartedlab_web.3 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
2twwicjssie9 getstartedlab_web.4 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
o4rk4x7bb3vm getstartedlab_web.5 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago


result of "docker-machine ls" :



    NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER     ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v18.09.0
myvm1 * virtualbox Running tcp://192.168.99.102:2376 v18.09.0
myvm3 - virtualbox Running tcp://192.168.99.103:2376 v18.09.0


test with curl



$ curl 192.168.99.102
curl: (7) Failed to connect to 192.168.99.102 port 80: Connection refused


How do i do to debug ?



I can give more information, if you want.



Thanks in advance.










share|improve this question

























  • How is your service defined? Did you publish a port and is the application listening on a port?

    – BMitch
    Jan 2 at 12:17











  • I'm going to add to the original message, the contents of docker-compose.yml

    – stack80
    Jan 2 at 12:57











  • I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

    – stack80
    Jan 2 at 13:03











  • Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

    – BMitch
    Jan 2 at 13:09











  • it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

    – stack80
    Jan 2 at 13:39
















0















i applied docker tutorial to set up a swarm.
I used docker toolbox, because i'm on windows 10 Family.



i step all statements, but at the end, the statement "curl ip_adress" doesn't run. error also with access on url.



$ docker --version
Docker version 18.03.0-ce, build 0520e24302


docker-compose.yml, located in /home/docker of virtual machine called "myvm1" :



version: "3"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
replicas: 5
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- "80:80"
networks:
- webnet
networks:
webnet:


swarm :



$ docker-machine ssh myvm1 "docker stack ps getstartedlab"
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
blmx8mldam52 getstartedlab_web.1 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
04ctl86chp6o getstartedlab_web.2 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
r3qyznllno9j getstartedlab_web.3 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
2twwicjssie9 getstartedlab_web.4 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
o4rk4x7bb3vm getstartedlab_web.5 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago


result of "docker-machine ls" :



    NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER     ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v18.09.0
myvm1 * virtualbox Running tcp://192.168.99.102:2376 v18.09.0
myvm3 - virtualbox Running tcp://192.168.99.103:2376 v18.09.0


test with curl



$ curl 192.168.99.102
curl: (7) Failed to connect to 192.168.99.102 port 80: Connection refused


How do i do to debug ?



I can give more information, if you want.



Thanks in advance.










share|improve this question

























  • How is your service defined? Did you publish a port and is the application listening on a port?

    – BMitch
    Jan 2 at 12:17











  • I'm going to add to the original message, the contents of docker-compose.yml

    – stack80
    Jan 2 at 12:57











  • I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

    – stack80
    Jan 2 at 13:03











  • Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

    – BMitch
    Jan 2 at 13:09











  • it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

    – stack80
    Jan 2 at 13:39














0












0








0








i applied docker tutorial to set up a swarm.
I used docker toolbox, because i'm on windows 10 Family.



i step all statements, but at the end, the statement "curl ip_adress" doesn't run. error also with access on url.



$ docker --version
Docker version 18.03.0-ce, build 0520e24302


docker-compose.yml, located in /home/docker of virtual machine called "myvm1" :



version: "3"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
replicas: 5
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- "80:80"
networks:
- webnet
networks:
webnet:


swarm :



$ docker-machine ssh myvm1 "docker stack ps getstartedlab"
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
blmx8mldam52 getstartedlab_web.1 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
04ctl86chp6o getstartedlab_web.2 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
r3qyznllno9j getstartedlab_web.3 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
2twwicjssie9 getstartedlab_web.4 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
o4rk4x7bb3vm getstartedlab_web.5 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago


result of "docker-machine ls" :



    NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER     ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v18.09.0
myvm1 * virtualbox Running tcp://192.168.99.102:2376 v18.09.0
myvm3 - virtualbox Running tcp://192.168.99.103:2376 v18.09.0


test with curl



$ curl 192.168.99.102
curl: (7) Failed to connect to 192.168.99.102 port 80: Connection refused


How do i do to debug ?



I can give more information, if you want.



Thanks in advance.










share|improve this question
















i applied docker tutorial to set up a swarm.
I used docker toolbox, because i'm on windows 10 Family.



i step all statements, but at the end, the statement "curl ip_adress" doesn't run. error also with access on url.



$ docker --version
Docker version 18.03.0-ce, build 0520e24302


docker-compose.yml, located in /home/docker of virtual machine called "myvm1" :



version: "3"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
replicas: 5
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- "80:80"
networks:
- webnet
networks:
webnet:


swarm :



$ docker-machine ssh myvm1 "docker stack ps getstartedlab"
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
blmx8mldam52 getstartedlab_web.1 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
04ctl86chp6o getstartedlab_web.2 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
r3qyznllno9j getstartedlab_web.3 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago
2twwicjssie9 getstartedlab_web.4 12081981/friendlyhello:part1 myvm1 Running Running 9 seconds ago
o4rk4x7bb3vm getstartedlab_web.5 12081981/friendlyhello:part1 myvm3 Running Running 6 seconds ago


result of "docker-machine ls" :



    NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER     ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v18.09.0
myvm1 * virtualbox Running tcp://192.168.99.102:2376 v18.09.0
myvm3 - virtualbox Running tcp://192.168.99.103:2376 v18.09.0


test with curl



$ curl 192.168.99.102
curl: (7) Failed to connect to 192.168.99.102 port 80: Connection refused


How do i do to debug ?



I can give more information, if you want.



Thanks in advance.







docker






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 2 at 13:00







stack80

















asked Jan 2 at 11:36









stack80stack80

33




33













  • How is your service defined? Did you publish a port and is the application listening on a port?

    – BMitch
    Jan 2 at 12:17











  • I'm going to add to the original message, the contents of docker-compose.yml

    – stack80
    Jan 2 at 12:57











  • I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

    – stack80
    Jan 2 at 13:03











  • Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

    – BMitch
    Jan 2 at 13:09











  • it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

    – stack80
    Jan 2 at 13:39



















  • How is your service defined? Did you publish a port and is the application listening on a port?

    – BMitch
    Jan 2 at 12:17











  • I'm going to add to the original message, the contents of docker-compose.yml

    – stack80
    Jan 2 at 12:57











  • I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

    – stack80
    Jan 2 at 13:03











  • Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

    – BMitch
    Jan 2 at 13:09











  • it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

    – stack80
    Jan 2 at 13:39

















How is your service defined? Did you publish a port and is the application listening on a port?

– BMitch
Jan 2 at 12:17





How is your service defined? Did you publish a port and is the application listening on a port?

– BMitch
Jan 2 at 12:17













I'm going to add to the original message, the contents of docker-compose.yml

– stack80
Jan 2 at 12:57





I'm going to add to the original message, the contents of docker-compose.yml

– stack80
Jan 2 at 12:57













I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

– stack80
Jan 2 at 13:03





I added to the original message, the contents of docker-compose.yml now. I publish on port 80 and application listen on port 80.

– stack80
Jan 2 at 13:03













Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

– BMitch
Jan 2 at 13:09





Add the output of docker run -it --rm --net container:$container_id nicolaka/netshoot ss -lnt where $container_id is from one of your containers.

– BMitch
Jan 2 at 13:09













it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

– stack80
Jan 2 at 13:39





it pulls the image, and at the end : C:Program FilesDocker Toolboxdocker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "ss-lnt": executable file not found in $PATH": unknown.

– stack80
Jan 2 at 13:39












1 Answer
1






active

oldest

votes


















0














Use of the routing mesh in Windows appears to be an EE only feature right now. You can monitor this docker for windows issue for more details. The current workaround is to use DNSRR internally and publish ports to the host directly instead of with the routing mesh. If you want your application to be reachable from any node in the cluster, this means you'd need to have a service on ever host in the cluster, scheduled globally, listening on the requested port. E.g.



version: "3.2"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
# global runs 1 on every node, instead of the replicated variant
mode: global
# DNSRR skips the VIP normally assigned to services
endpoint_mode: dnsrr
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- target: 80
published: 80
protocol: tcp
# host publishes the port directly from the container without the routing mesh
mode: host
networks:
- webnet
networks:
webnet:





share|improve this answer
























  • Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

    – stack80
    Jan 2 at 21:30













  • Localhost might work with an ssh, otherwise your vm's are different from localhost.

    – BMitch
    Jan 2 at 22:11











  • Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

    – stack80
    Jan 3 at 10:11











  • i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

    – stack80
    Jan 3 at 12:01











  • From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

    – BMitch
    Jan 3 at 13:28











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54005625%2fdocker-swarm-with-docker-toolbox-doesnt-run%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









0














Use of the routing mesh in Windows appears to be an EE only feature right now. You can monitor this docker for windows issue for more details. The current workaround is to use DNSRR internally and publish ports to the host directly instead of with the routing mesh. If you want your application to be reachable from any node in the cluster, this means you'd need to have a service on ever host in the cluster, scheduled globally, listening on the requested port. E.g.



version: "3.2"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
# global runs 1 on every node, instead of the replicated variant
mode: global
# DNSRR skips the VIP normally assigned to services
endpoint_mode: dnsrr
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- target: 80
published: 80
protocol: tcp
# host publishes the port directly from the container without the routing mesh
mode: host
networks:
- webnet
networks:
webnet:





share|improve this answer
























  • Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

    – stack80
    Jan 2 at 21:30













  • Localhost might work with an ssh, otherwise your vm's are different from localhost.

    – BMitch
    Jan 2 at 22:11











  • Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

    – stack80
    Jan 3 at 10:11











  • i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

    – stack80
    Jan 3 at 12:01











  • From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

    – BMitch
    Jan 3 at 13:28
















0














Use of the routing mesh in Windows appears to be an EE only feature right now. You can monitor this docker for windows issue for more details. The current workaround is to use DNSRR internally and publish ports to the host directly instead of with the routing mesh. If you want your application to be reachable from any node in the cluster, this means you'd need to have a service on ever host in the cluster, scheduled globally, listening on the requested port. E.g.



version: "3.2"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
# global runs 1 on every node, instead of the replicated variant
mode: global
# DNSRR skips the VIP normally assigned to services
endpoint_mode: dnsrr
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- target: 80
published: 80
protocol: tcp
# host publishes the port directly from the container without the routing mesh
mode: host
networks:
- webnet
networks:
webnet:





share|improve this answer
























  • Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

    – stack80
    Jan 2 at 21:30













  • Localhost might work with an ssh, otherwise your vm's are different from localhost.

    – BMitch
    Jan 2 at 22:11











  • Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

    – stack80
    Jan 3 at 10:11











  • i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

    – stack80
    Jan 3 at 12:01











  • From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

    – BMitch
    Jan 3 at 13:28














0












0








0







Use of the routing mesh in Windows appears to be an EE only feature right now. You can monitor this docker for windows issue for more details. The current workaround is to use DNSRR internally and publish ports to the host directly instead of with the routing mesh. If you want your application to be reachable from any node in the cluster, this means you'd need to have a service on ever host in the cluster, scheduled globally, listening on the requested port. E.g.



version: "3.2"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
# global runs 1 on every node, instead of the replicated variant
mode: global
# DNSRR skips the VIP normally assigned to services
endpoint_mode: dnsrr
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- target: 80
published: 80
protocol: tcp
# host publishes the port directly from the container without the routing mesh
mode: host
networks:
- webnet
networks:
webnet:





share|improve this answer













Use of the routing mesh in Windows appears to be an EE only feature right now. You can monitor this docker for windows issue for more details. The current workaround is to use DNSRR internally and publish ports to the host directly instead of with the routing mesh. If you want your application to be reachable from any node in the cluster, this means you'd need to have a service on ever host in the cluster, scheduled globally, listening on the requested port. E.g.



version: "3.2"
services:
web:
# replace username/repo:tag with your name and image details
image: 12081981/friendlyhello:part1
deploy:
# global runs 1 on every node, instead of the replicated variant
mode: global
# DNSRR skips the VIP normally assigned to services
endpoint_mode: dnsrr
resources:
limits:
cpus: "0.1"
memory: 50M
restart_policy:
condition: on-failure
ports:
- target: 80
published: 80
protocol: tcp
# host publishes the port directly from the container without the routing mesh
mode: host
networks:
- webnet
networks:
webnet:






share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 2 at 20:09









BMitchBMitch

64.5k10139160




64.5k10139160













  • Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

    – stack80
    Jan 2 at 21:30













  • Localhost might work with an ssh, otherwise your vm's are different from localhost.

    – BMitch
    Jan 2 at 22:11











  • Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

    – stack80
    Jan 3 at 10:11











  • i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

    – stack80
    Jan 3 at 12:01











  • From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

    – BMitch
    Jan 3 at 13:28



















  • Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

    – stack80
    Jan 2 at 21:30













  • Localhost might work with an ssh, otherwise your vm's are different from localhost.

    – BMitch
    Jan 2 at 22:11











  • Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

    – stack80
    Jan 3 at 10:11











  • i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

    – stack80
    Jan 3 at 12:01











  • From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

    – BMitch
    Jan 3 at 13:28

















Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

– stack80
Jan 2 at 21:30







Thanks a lot. It runs ! i teared down the app and the swarm, used your new docker-compose.yml docker-machine ssh myvm1 "curl ip_address" : OK with 192.168.99.102, 192.168.99.103, localhost. with web browser, it's ok but not for localhost. For the tutorial "container", it runs for 192.168.99.102, not for localhost. i wonder why the curl command ran with localhost

– stack80
Jan 2 at 21:30















Localhost might work with an ssh, otherwise your vm's are different from localhost.

– BMitch
Jan 2 at 22:11





Localhost might work with an ssh, otherwise your vm's are different from localhost.

– BMitch
Jan 2 at 22:11













Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

– stack80
Jan 3 at 10:11





Thanks a lot. I read issue that you have quoted. I'm going to continue docker tutorials. I hope that i haven't others problems, cause by docker toolbox version.

– stack80
Jan 3 at 10:11













i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

– stack80
Jan 3 at 12:01





i didn't find to get 5 instances (subtitute "replica" option). Have you an idea please ?

– stack80
Jan 3 at 12:01













From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

– BMitch
Jan 3 at 13:28





From the comment in the file above: "global runs 1 on every node, instead of the replicated variant"

– BMitch
Jan 3 at 13:28




















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54005625%2fdocker-swarm-with-docker-toolbox-doesnt-run%23new-answer', 'question_page');
}
);

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







wUoAsNP4Gsc,1BamKQDhlc2Xwt,MLz,AGmcUyzG3Rus0tWOhh4t,ADMb2QoqmX,YrAC AzMrcsNGkYv5E R
4Y 4KKoKfw28l5aq ji94 o1,g,TKKTHnWz0SjWc

Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas