It is affecting package docker-engine now, since yesterday on my pc.
Same symptoms (docker networking works only for a single shot after each
restart), no /etc/network/interfaces entry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello.
Same behavior as Victor Pal described in #7 appears on Debian Jessie laptop
with docker-engine from https://apt.dockerproject.org/repo.
Found that in my case the problem appears only if exists a
/etc/network/interfaces entry like 'iface docker0 inet manual' that I used to
prevent
Seems to be fixed in 16.04 beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509867
Title:
docker network connection only working after daemon restart
To manage notifications about this bug go
I still have the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509867
Title:
docker network connection only working after daemon restart
To manage notifications about this bug go to:
I have no idea what happened but I can't reproduce this any more.
I checked my apt logs and there is no sign that the docker.io package was
updated.
Maybe it was caused by some other bug in another package that was fixed
meanwhile.
Can anyone else who could reproduce this confirm that this
It seems that the issue is that the route to the docker network namespace does
not exist after the OS starts up, so this rule is missing on my desktop:
172.17.0.0 0.0.0.0 255.255.0.0 U 0 00 docker0
Because this is missing packages that would target the container
** Changed in: docker.io (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509867
Title:
docker network connection only working after daemon restart
To
Hi,
I could reproduce with a full blown ubuntu, I'm trying to find the
issue.
With docker inspect, you can get the Pid of the container you want to debug on.
Then as root you create if it doesn't exist /var/run/netns, then you link
/proc/$pid/ns/net /var/run/netns/container_name.
Then you can
** Changed in: docker.io (Ubuntu)
Assignee: (unassigned) => Kick In (kick-d)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509867
Title:
docker network connection only working after daemon
Hi,
Thanks for your report.
I tried to reproduce on a minimal ubuntu install, steps I've done yet:
1- install docker on vivid host (1.5.0, for now), start an openssh-server
container
2-so-release-upgrade of the vivid host to wily host (upgraded to
docker.io-1.6.2)
3-after reboot start
Yep, upgrade was done from vivid to wily.
Can you point me to some tools to discover the state of namespace networks so I
can do some investigation myself?
>From what I have seen iptables rules are in place and the docker0 interface
>exists when network connection fails.
I was thinking that
It seems to be a networking issue as I am unable to connect to a
forwarded port until I reload the daemon.
For example if you run `sudo docker run -it -p 1080:1080 -P
jamesdbloom/mockserver` and then try to connect to http://localhost:1080
in your browser, you should get a 404 (MockServer's
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509867
Title:
** Description changed:
- I have just upgraded to Ubuntu 15.10 and realized when I trie to ssh into my
container I get the following error message:
+ I have just upgraded to Ubuntu 15.10 and realized when I try to ssh into my
container I get the following error message:
14 matches
Mail list logo
