Cloudera Docker Image running on hyper-v docker host access from Windows OS
up vote
0
down vote
favorite
Set-up
- Windows 10 PC
- Docker running on MobyLinuxVM on Hyper-V
- Cloudera container running
Network between Windows PC and Hyper-V is internal DockerNAT switch
This is working as expected, I can access internet from MobyLinux and Container
ifconfig commands
- From windows IPv4 Address. . . . . . . . . . . : 192.168.xx.xx
- From DockerHost eth0 .... : 192.168.yy.y
- From Container is the same (this is because I started the image to use network=host, which also means ports are automatically mapped if my understanding is correct)
I verified the cloudera admin manager is running
service cloudera-scm-service status
I have checked with curl that I can access the manager from Dockerhost and the container
curl -u 'admin:admin' http://192.168.yy.y:7180
However, I want to open that admin console on my windows desktop.
I dont understand what I am doing wrong.
I think the problem is between my windows machine and hyper-v
Why can't I ping the dockerhost VM from wy windows desktop?
docker hyper-v docker-networking cloudera-manager
add a comment |
up vote
0
down vote
favorite
Set-up
- Windows 10 PC
- Docker running on MobyLinuxVM on Hyper-V
- Cloudera container running
Network between Windows PC and Hyper-V is internal DockerNAT switch
This is working as expected, I can access internet from MobyLinux and Container
ifconfig commands
- From windows IPv4 Address. . . . . . . . . . . : 192.168.xx.xx
- From DockerHost eth0 .... : 192.168.yy.y
- From Container is the same (this is because I started the image to use network=host, which also means ports are automatically mapped if my understanding is correct)
I verified the cloudera admin manager is running
service cloudera-scm-service status
I have checked with curl that I can access the manager from Dockerhost and the container
curl -u 'admin:admin' http://192.168.yy.y:7180
However, I want to open that admin console on my windows desktop.
I dont understand what I am doing wrong.
I think the problem is between my windows machine and hyper-v
Why can't I ping the dockerhost VM from wy windows desktop?
docker hyper-v docker-networking cloudera-manager
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Set-up
- Windows 10 PC
- Docker running on MobyLinuxVM on Hyper-V
- Cloudera container running
Network between Windows PC and Hyper-V is internal DockerNAT switch
This is working as expected, I can access internet from MobyLinux and Container
ifconfig commands
- From windows IPv4 Address. . . . . . . . . . . : 192.168.xx.xx
- From DockerHost eth0 .... : 192.168.yy.y
- From Container is the same (this is because I started the image to use network=host, which also means ports are automatically mapped if my understanding is correct)
I verified the cloudera admin manager is running
service cloudera-scm-service status
I have checked with curl that I can access the manager from Dockerhost and the container
curl -u 'admin:admin' http://192.168.yy.y:7180
However, I want to open that admin console on my windows desktop.
I dont understand what I am doing wrong.
I think the problem is between my windows machine and hyper-v
Why can't I ping the dockerhost VM from wy windows desktop?
docker hyper-v docker-networking cloudera-manager
Set-up
- Windows 10 PC
- Docker running on MobyLinuxVM on Hyper-V
- Cloudera container running
Network between Windows PC and Hyper-V is internal DockerNAT switch
This is working as expected, I can access internet from MobyLinux and Container
ifconfig commands
- From windows IPv4 Address. . . . . . . . . . . : 192.168.xx.xx
- From DockerHost eth0 .... : 192.168.yy.y
- From Container is the same (this is because I started the image to use network=host, which also means ports are automatically mapped if my understanding is correct)
I verified the cloudera admin manager is running
service cloudera-scm-service status
I have checked with curl that I can access the manager from Dockerhost and the container
curl -u 'admin:admin' http://192.168.yy.y:7180
However, I want to open that admin console on my windows desktop.
I dont understand what I am doing wrong.
I think the problem is between my windows machine and hyper-v
Why can't I ping the dockerhost VM from wy windows desktop?
docker hyper-v docker-networking cloudera-manager
docker hyper-v docker-networking cloudera-manager
asked Nov 18 at 14:55
Nanotron
417
417
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53362203%2fcloudera-docker-image-running-on-hyper-v-docker-host-access-from-windows-os%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