New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Containers fail to keep running since latest Docker update #1809

Closed
noefingway opened this Issue Jul 2, 2017 · 10 comments

Comments

Projects
None yet
8 participants
@noefingway

noefingway commented Jul 2, 2017

Expected behavior

docker app runs until I stop it

Actual behavior

all containers fail after several hours, this has only started since the latest update

Information

  • Full output of the diagnostics from "Diagnose & Feedback" in the menu

Docker for Mac: version: 17.06.0-ce-mac18 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.11.6 (build: 15G1510)
logs: /tmp/EDB656CD-E5D0-4093-9592-E5B2D11106B8/20170702-182642.tar.gz
[OK] db.git
[OK] vmnetd
[OK] dns
[OK] driver.amd64-linux
[OK] virtualization VT-X
[OK] app
[OK] moby
[OK] system
[OK] moby-syslog
[OK] db
[OK] env
[OK] virtualization kern.hv_support
[OK] slirp
[OK] osxfs
[OK] moby-console
[OK] logs
[OK] docker-cli
[OK] menubar
[OK] disk

Steps to reproduce the behavior

Seems happen to any container I run.

@junian

This comment has been minimized.

Show comment
Hide comment
@junian

junian Jul 2, 2017

Happened to me, too. I run a mysql container. Usually it's running without problem. Now it's closing every time I sleep my Mac.

junian commented Jul 2, 2017

Happened to me, too. I run a mysql container. Usually it's running without problem. Now it's closing every time I sleep my Mac.

@djs55

This comment has been minimized.

Show comment
Hide comment
@djs55

djs55 Jul 3, 2017

Contributor

In the logs for EDB656CD-E5D0-4093-9592-E5B2D11106B8:

<Warning>: Triggering a VM reboot because proxy settings changed from 
main.proxySettings{http:"", https:"", exclude:""} to main.proxySettings{http:"", https:"", exclude:"*.local, 169.254/16"}

HTTP proxies are configured by modifying the environment variables inside the VM, which requires a VM restart whenever the variables change. In this case perhaps it's unnecessary to reboot when the exclude changes, when there is no actual proxy set.

As a workaround try setting: Whale Menu -> Proxies -> No proxies.

Contributor

djs55 commented Jul 3, 2017

In the logs for EDB656CD-E5D0-4093-9592-E5B2D11106B8:

<Warning>: Triggering a VM reboot because proxy settings changed from 
main.proxySettings{http:"", https:"", exclude:""} to main.proxySettings{http:"", https:"", exclude:"*.local, 169.254/16"}

HTTP proxies are configured by modifying the environment variables inside the VM, which requires a VM restart whenever the variables change. In this case perhaps it's unnecessary to reboot when the exclude changes, when there is no actual proxy set.

As a workaround try setting: Whale Menu -> Proxies -> No proxies.

@vyscond

This comment has been minimized.

Show comment
Hide comment
@vyscond

vyscond Jul 3, 2017

Sounds like this trick from @djs55 also resolves the annoying reboot that happens every single time i switch from network.

vyscond commented Jul 3, 2017

Sounds like this trick from @djs55 also resolves the annoying reboot that happens every single time i switch from network.

@thaJeztah

This comment has been minimized.

Show comment
Hide comment
@thaJeztah

thaJeztah Jul 4, 2017

Member

@djs55 something for the troubleshooting section in the documentation perhaps?

Member

thaJeztah commented Jul 4, 2017

@djs55 something for the troubleshooting section in the documentation perhaps?

@djs55

This comment has been minimized.

Show comment
Hide comment
@djs55

djs55 Jul 4, 2017

Contributor

The unnecessary reboot caused by the exclude changing when there is no proxy set has been cherry-picked into the branch for 17.06.1, which should hopefully be released later this week. Thanks for your report!

Contributor

djs55 commented Jul 4, 2017

The unnecessary reboot caused by the exclude changing when there is no proxy set has been cherry-picked into the branch for 17.06.1, which should hopefully be released later this week. Thanks for your report!

@noefingway

This comment has been minimized.

Show comment
Hide comment
@noefingway

noefingway Jul 4, 2017

Setting "No Proxies" appears to have solved the problem. thx!

noefingway commented Jul 4, 2017

Setting "No Proxies" appears to have solved the problem. thx!

@timothyallan

This comment has been minimized.

Show comment
Hide comment
@timothyallan

timothyallan Jul 17, 2017

Hopefully this also fixes the issue of restarting Docker when stopping/starting Charles Proxy!

timothyallan commented Jul 17, 2017

Hopefully this also fixes the issue of restarting Docker when stopping/starting Charles Proxy!

@vyscond

This comment has been minimized.

Show comment
Hide comment
@vyscond

vyscond Jul 22, 2017

@timothyallan It does. Just confirmed it.

vyscond commented Jul 22, 2017

@timothyallan It does. Just confirmed it.

@timothyallan

This comment has been minimized.

Show comment
Hide comment
@timothyallan

timothyallan Jul 22, 2017

@vyscond Hmmm, yours doesn't do this if you're using the system proxy?

#1873 (comment)

timothyallan commented Jul 22, 2017

@vyscond Hmmm, yours doesn't do this if you're using the system proxy?

#1873 (comment)

@docker-for-desktop-robot

This comment has been minimized.

Show comment
Hide comment
@docker-for-desktop-robot

docker-for-desktop-robot Mar 27, 2018

Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Collaborator

docker-for-desktop-robot commented Mar 27, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment