ko
Moby
Our great sponsors
ko | Moby | |
---|---|---|
28 | 212 | |
7,219 | 67,655 | |
3.6% | 0.4% | |
9.0 | 10.0 | |
6 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ko
-
Distroless container images with Apko from Chainguard
Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.
-
What is the most common approach to configure a backend app?
- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile
-
Tool to build Docker images
ko
- how to create container for Kubernetes?
-
Golang Backend in Production
You don't need to write and manage Dockerfiles. Simply just use ko: https://github.com/google/ko (You also don't need Docker Engine)
-
How to containerize your Go app in 10 minutes!
Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko
-
Containerd... Do I use Docker to build the container image? I miss the Docker Shim
Here is link number 1 - Previous text "ko"
-
HOWTO: Generate Go based multiarch images the easy way
It depends on your use case, but have you ever tried google/ko?
-
`COPY --chmod` reduced the size of my container image by 35%
If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.
-
`COPY –chmod` reduced the size of my container image by 35%
I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko
Moby
-
Release Radar • March 2024 Edition
Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.
-
Choosing a Name for Your Computer
Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...
- Docker Inc. refuses to patch HIGH vulnerabilities in Docker
-
Do not install Docker Desktop on GNU/Linux systems
Try to use moby instead since that is the engine in Docker.
-
Exploring Podman: A More Secure Docker Alternative
> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.
Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780
It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)
- Moby: Block io_uring_* syscalls in default profile
- Io_uring will be blocked by default on Docker
-
OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
Perhaps.
Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.
Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.
-
The Twelve-Factor App
AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...
What are some alternatives?
kaniko - Build Container Images In Kubernetes
podman - Podman: A tool for managing OCI containers and pods.
Pomerium - Pomerium is an identity and context-aware reverse proxy for zero-trust access to web applications and services.
containerd - An open and reliable container runtime
golang-sample-app - Example application with Golang and Docker
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
docker-openwrt - OpenWrt running in Docker
Dockerfile-Generator - dfg - Generates dockerfiles based on various input channels.
ofelia - A docker job scheduler (aka. crontab for docker)
distroless - 🥑 Language focused docker images, minus the operating system.
k3d - Little helper to run CNCF's k3s in Docker