roadmap VS docker

x86-64 containers?

https://github.com/docker/roadmap/issues/384 is still open. :(

Request features or give feedback: https://github.com/docker/roadmap/issues/524

Nothing in the road map [Github] returned by searching 'stop'.

Further reading online revealed that host network mode is not available for swarm started with docker stack deploy. (Possible related open issue: github link).

Single-click k8s install. Extensions. Init. And there are people who just prefer an app-based experience for their own reasons - I think it was the most "upvoted" request ever on their public roadmap.

In case you need to run x86 containers: Docker has Rosetta support now but it's buggy.

https://github.com/docker/roadmap/issues/384

Without Rosetta it uses relatively slow Qemu emulation.

https://github.com/docker/roadmap/issues/44

So, at the moment, any public organization images are doomed to be lost, if they won't pay.

I've been watching this GitHub issue for damn near 3 years. Filesystem performance is pretty bad, depending on what you're doing. I had to kludge together workarounds to my DX at my last role where we used Docker for development. It was really, really painful and distracting.

[2] https://github.com/docker/roadmap/issues/7

Everything is working fine, but it is not currently doing the automatic code reload. I tried mounting the volume but there is some conflict with the way docker and virtualbox handles files such that the conflict leads to file changes from the host not reflected in docker container. (That's not the first link I have that appears related to this problem, it's just the first I found while googling it on another day)...

github.com/docker/docker/client

Moby is the core of Docker. https://github.com/docker/docker redirects to it.

Docker however has made some major screwups in their IPv6 implementation, so it’s not so trivial as you’d expect it to be. There’s a whole discussion about it here: https://github.com/docker/docker.github.io/issues/6075 but the gist is: Docker cannot auto-assign addresses (SLAAC) like a normal endpoint, it also cannot request a prefix (DHCPv6 PD) like a router, you have to set it all up manually.

[1] https://github.com/docker/docker.github.io/issues/5325

That said, Swarm is definitely in maintenance mode, which is actually how some people like it, given that this means pretty good stability for the current features, instead of breaking changes, which are a slightly larger concern in the case of Kubernetes. However, this also means that new features will get implemented only occasionally, if ever - the last big one that i recall was Swarm jobs. Essentially, i'd say that it's still just a question of time until Swarm dies, but for now it's in the sweet spot of stability and usability if all that you need is a pretty simple and lightweight orchestrator.

From scrounging through the internet, my understanding is if multiple docker containers are run based on the same image, the only extra disk space used is what the writable layer uses and the read-only image data is shared by all the containers. https://github.com/docker/docker.github.io/issues/1520#issuecomment-305179362

Wowww: https://github.com/docker/docker.github.io/issues/6910#issue...

What the hell does "Docker's new direction to go back to its roots and focus on developer tooling" even mean? Docker is developer tooling, that's the whole product. That's not "going back to your roots" that's just doing your damn job.