GitHub Package Registry VS runc

GitHub Package Registry is a package hosting service provided by GitHub. It allows you to publish, share, and manage software packages directly within your GitHub repositories. - Source: dev.to / 5 months ago

Ideally you run your the build step on CI and push the built image into container registry (like dockerhub or ghcr). You can then download the image on server and run it. You can do this with docker-compose as well, just use the image instead of dockerfile to define your web app like you do with proxy and DB. Source: about 1 year ago

Package Hosting & Container Registry (Free for public repos,500 MB storage & 1GB bandwidth outside CI/CD free for private repos). - Source: dev.to / over 1 year ago

There are more Container registries but Docker Hub, such as Github Registry, Amazon ECR, to name a few. We can change the registry anytime by using the command docker login. - Source: dev.to / over 1 year ago

You can use your github account as your own NPM registry using github packages. Source: almost 2 years ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / 8 months ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 1 year ago

Your Docker Container can only run Linux. That's because Docker takes advantage of runC which uses the Linux kernel. You can't run Windows inside of Docker. But of course you can run Docker on a Windows host machine. If you are running a .NET project, you won't be able to use Docker. On the other hand, if you're running .NET Core then you're in luck! - Source: dev.to / over 1 year ago

This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility... - Source: dev.to / almost 2 years ago

If you are curious about how exactly Docker does this I urge to have a look at the following links on layered file system and the library runc and also this great wikipedia overview of Docker. - Source: dev.to / almost 2 years ago