I still can't bind mount a file in a container if that file already exists in that containter. Is this production ready?
Docker for Mac and Windows Is Now Generally Available and Ready for Production
111–120 of 169 posts
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#112I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…
I can't get it to work on OSX without the CPU staying at 100%. Still not fixed:
> There are several other threads on this topic already. Setups that docker build an image and rely on in-Docker storage work well; setups that rely heavily on bind-mounting host directories do not. A complex npm install in a bind-mounted directory breaks Docker entirely, according to at least one thread here.
https://forums.docker.com/t/just-switched-over-from-dlite-cp...
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#113An interesting fact I think is worth mentioning is that Docker for Mac uses a forked and currently closed version of xhyve, and not the same xhyve that we can find on Github. The last commit to open source xhyve was May 27. With that said Docker has plans to open source it, I wonder if that will happen soon as they declare Docker for Mac ready for production. That would imply that the xhyve port also should be ready…
I think this is what you're looking for: https://github.com/docker/hyperkit Source: https://blog.docker.com/2016/05/docker-unikernels-open-sourc...
Oh, my bad, thanks for the correction! :)
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#114Earlier quoted context omitted.
I have also yet to see a reasonable solution for connecting out of a container back to the host with Docker.app. On linux and OSX with docker-machine this is easy with: docker run --add-host host:ip.for.docker.interface foo But there is no equivalent to the docker0 interface or the vboxnet interface for Docker.app. EDIT: I don't use this for any production environments, but it is very useful for debugging and testing…
The best solution is to add a new stable, unconflicting IP address to the loopback interface on the Mac and connect to that.
Still not as friendly, as it requires system changes on the host, but not totally unreasonable.
I'll give it a try if I evaluate Docker.app again.
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#115I still can't bind mount a file in a container if that file already exists in that containter. Is this production ready?
This seems to work fine for me:
docker run -it -v /private/etc/passwd:/etc/passwd alpine sh (not recommended for any actual use obviously)
Is there a particular case in which this failed for you? We'd appreciate a bug report on https://github.com/docker/for-mac/issues (or from the Docker for Mac GUI, just click on "Diagnose and Feedback") so we can chase down whatever issue you're having.
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#116I still can't bind mount a file in a container if that file already exists in that containter. Is this production ready?
This seems to work fine for me: docker run -it -v /private/etc/passwd:/etc/passwd alpine sh (not recommended for any actual use obviously) Is there a particular case in which this failed for you? We'd appreciate a bug report on https://github.com/docker/for-mac/issues (or from the Docker for Mac GUI, just click on "Diagnose and Feedback") so we can chase down whatever issue you're having.
Yes, this use case, it happens on Windows and on Mac as well.
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: rootfs_linux.go:53: mounting "/var/lib/docker/aufs/mn t/90d24356afdeb7b9ddad4b3b6903be92063151c33bf34f3d63ede464437060c6/cryptoservice/broker-config.yml" to rootfs "/var/lib/docker/aufs/mnt/90d24356afdeb7b9ddad4 b3b6903be92063151c33bf34f3d63ede464437060c6" caused "not a directory".
(I'm mounting broker-config.yml and that file is already present in the container. Most recent Docker for Win beta in this case, but getting the same on non-beta Docker for Mac.)
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#117Earlier quoted context omitted.
This isn't a product that's "ready for production"; it's a product company declaring that it is. This means what it's always meant: that the company believes the sum they'll make by convincing people it's "production ready" is greater than the sum they'll lose from people realizing it isn't. Keep in mind the optimal state of affairs for Docker Inc. is one where everyone is using Docker and everyone requires an enterp…
So misinformed. Docker for mac and docker for windows are not targeting production. They are designed for local dev envs
So why call it "production ready"?
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#118I'm finding it really funny how even Docker users can't really explain easily what Docker is.
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#119I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…
This is another issue that's been preventing my adoption of Docker for Mac: https://forums.docker.com/t/docker-pull-not-using-correct-dn... . The fact that DNS resolution over a VPN still doesn't work correctly makes me wonder how production-worthy this release is. It's a pretty common thing people want to do in my experience.
If you have the time, could you make a report on the issue tracker https://github.com/docker/for-mac/issues and include the contents of /etc/resolv.conf and "scutil --dns" when you connect and disconnect to your VPN? Ideally also include an example resolution of a name by the host with something like "dig @server internalname". I suspect the problem is caused by a DNS server in the "scutil" list being missing from /etc/resolv.conf. We're planning on watching the "scutil --dns" list for changes, but it's not implemented completely yet.
Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production
#120Earlier quoted context omitted.
So misinformed. Docker for mac and docker for windows are not targeting production. They are designed for local dev envs
So why call it "production ready"?
I agree that it is confusing. Production ready in the sense that it is stable for the targeted use-case: local development environments. Not for "production". Damn now i'm confused...