go-layout VS Moby

You can download the full project layout template from my GitHub (https://github.com/fir1/go-layout).

Docker itself is open-source, and has slowly been broken down into modular components that are themselves open-source. For example, most of what "run this Docker container" does has been extracted out into containerd, which is Apache licensed and used by lots of things. The Docker CE engine is now based on Moby, also Apache license, and the docker command line tool is also Apache licensed. I expect these tools to continue to be community-maintained (though maybe without the Docker name) due to their immense popularity even Docker Inc folds.

This was the proposed PR that is summarized in that article: https://github.com/moby/moby/pull/10411

if you did `docker tag supersecret/app:latest && docker push` instead of `docker tag registry.corp.com/supersecret/app:latest` guess where your code just went?

Same on the pull side, if you wanted your corp's ubuntu base rather than just `docker pull ubuntu`.

This is all part of docker's master plan.

You can see it with more clarity here:

https://github.com/moby/moby/issues/11815

or here:

https://stackoverflow.com/questions/33054369/how-to-change-t...

so redhat's podman clone of docker allows this:

https://halukkarakaya.medium.com/how-to-configure-default-se...

This is probably the wrong link. The website is: https://mobyproject.org/

Which I flipped through and also watched the video: https://www.youtube.com/watch?v=jcRR0g0kO4o&t=1s

I still have zero clue what this is, how to use it, who it is for, and how it works.

It is a long standing issue and is a gotcha for everyone.

https://github.com/moby/moby/issues/22054

It's completely asinine.

This is the kind of case that is a good argument for some liability regulation for companies that just make calculated selfish tradeoffs against user security. The bug[1] is a hair under 7 years old and it's obviously burned a lot of people all over the world.

[1] https://github.com/moby/moby/issues/22054

The article links to a github project on moby/moby talking about containerd integration work. Looking at the release notes for Docker 23, it calls out https://github.com/moby/moby/pull/43887 as being added, and I think this is what they maybe were talking about. It's really just removing a dependency on a runsc compatible shim, and more directly integrating with any oci-compliant containerd runtime without the implicit shim dependency.