image-spec
runtime-spec
image-spec | runtime-spec | |
---|---|---|
25 | 11 | |
3,254 | 3,087 | |
1.1% | 0.6% | |
7.4 | 6.4 | |
8 days ago | 27 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.
image-spec
-
Understanding Buildpacks in Cloud Native Buildpacks
A buildpack is a software, designed to transform application source code into executable (OCI) images that can run on a variety of cloud platforms. At its core, a buildpack is a directory that includes a specific file named buildpack.toml. This file contains metadata and configuration details that dictate how the buildpack should behave. Buildpacks in simple terms, is a set of standards defining how the different steps that are required to build a compliant container image can be automated. Using those standards, there are projects that have been built round enabling that using an CLI or an API. The most common way of doing that is through the Cloud Native Buildpacks' Pack project. Pack is a CLI command that can run in the same system the developers are using to actually go through creating a Dockerfile.
-
Dive: A tool for exploring a Docker image, layer contents and more
Eventually, once zstd support gets fully supported, and tiny gzip compression windows are not a limitation, then compressing a full layer would almost certainly have a better ratio over several smaller layers
https://github.com/opencontainers/image-spec/issues/803
- Homelab advice
- Containers - entre historia y runtimes
-
Is labelling best practice?
Please note that label-schema has been superseded by https://github.com/opencontainers/image-spec/blob/main/annotations.md<^
-
Pushing container images to GitHub Container Registry with GitHub Actions
GitHub Container Registry stores container images within your organization or personal account, and allows you to associate an image with a repository. It currently supports both the Docker Image Manifest V2, Schema 2 and Open Container Initiative (OCI) specifications.
-
The cloud-agnostic-architecture illusion
We build all services as containerized workloads, i.e., OCI images - sometimes called Docker images. We deploy these to the Kubernetes product offered by the cloud vendor. Whenever we need some capability, containers are the answer. This insulates our applications from the vendor. In principle, we could switch providers as long as Kubernetes is available.
-
Containerd... Do I use Docker to build the container image? I miss the Docker Shim
Build images with anything that makes OCI compliant images, push, and profit.
-
Opensource Server Hosting/Management Web Panel
it's funny that you mention this because it is actually the thing that is next on my agenda for the image, as you can probably see already I bake in OCI image annotations in our image, which is great for including some core pieces of meta data. In addition to this though I will soon be including custom labels for Base64 encoded YAMLs for Kubernetes deployments using this image. I will look at including helm configuration as well. Then it should be just as easy as: $ docker pull registry.gitlab.com/crafty-controller/crafty-4:latest $ docker image inspect registry.gitlab.com/crafty-controller/crafty-4:latest | jq -r ".[].Config.Labels.\"org.arcadiatech.crafty.k8s.deployment\"" | base64 -d | kubectl apply -f -
-
My director is mad that I accepted another internal position for a 26% raise when he was told he could only give me a 10%
They still don't do anything really of substance, they're just gateways to their vendor's world - booking systems, payment systems, etc. You learn those as you go along. Yes, as a potential employee, you need to be able to tick those boxes on your CV, but if you understand the underlying technology, it's mostly a matter of booking your own AWS or Azure server for $5-10 a month for a few weeks, and fooling around. (Docker is a bit different in the sense that they were the first to popularize today's de-facto container image standard, the "Docker container", which has since been accepted as a proper standard and renamed to "OCI image format"; but at the end of the day, at this point in time, Docker in itself is still just a company out for the money, and the multi-GB installation of their product can, for the essential functionality part, be replaced by a few hundred lines of Bash code. The cool boys today don't use Docker, they use [Podman(https://podman.io/), which is essentially a much more lightweight drop-in replacement ;-) )
runtime-spec
-
The What, Why and How of Containers
> Well, no. When people say "containers", they always mean "Docker".
Not really/necessarily. https://github.com/opencontainers/runtime-spec
-
Containers - entre historia y runtimes
Otras iniciativas empezaron a surgir debido a la alta popularidad de los containers y debido a esto, en 2015 se crea OCI(Open Container Initiative) para definir un estandar para containers(runtimes e imagenes).
-
Docker is deleting Open Source organisations - what you need to know
Theoretically there could be a lot of new options that pop up. There is an Open Container Initiative that has a Runtime Specification that can be implemented. youki is one example of an OCI-compliant container runtime.
-
Container Deep Dive Part 1: Container Runtime
Open Container Initiative Runtime Specification aims to specify the configuration, execution environment, and lifecycle of a container. Source
- Podman + minikube
-
Podman/buildah oci bundle
How I can generate oci bundle that can be run with systemd-nspawn? I've tried podman/buildah push, but generated directory/archive is not an oci bundle (https://github.com/opencontainers/runtime-spec/blob/main/bundle.md). I've tried podman image mount, but config.json file is nowhere to be found. It looks like I am missing something simple.
-
Youki, a container runtime written in Rust that has passed all integration tests provided by OCI(Open Container Initiative).
In more detail, runC and youki need to implement this specification. https://github.com/opencontainers/runtime-spec
- Youki – OCI container runtime with support for cgroup2 written in Rust
-
Kubernetes vs Docker: Understanding Containers in 2021
A runtime specification that describes how to unpack and run a container. OCI maintains a reference implementation called runc. Both containerd and CRI-O use runc in the background to spawn containers.
-
Experimental implementation of container runtime in Rust
The immediate goal of this project(youki) is to pass all the default tests of the runtime-spec that the opencontainers is making. Of course, this is for my own learning, but I believe Rust is one of the best languages to implement a container runtime.
What are some alternatives?
skopeo - Work with remote images registries - retrieving information, images, signing content
youki - A container runtime written in Rust
ovh-ipxe-customer-script - Boot OVH server with your own iPXE script
podman - Podman: A tool for managing OCI containers and pods.
distroless - 🥑 Language focused docker images, minus the operating system.
containerd - An open and reliable container runtime
flyctl - Command line tools for fly.io services
cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface
asmttpd - Web server for Linux written in amd64 assembly.
runc - CLI tool for spawning and running containers according to the OCI specification
dive - A tool for exploring each layer in a docker image
crun - A fast and lightweight fully featured OCI runtime and C library for running containers