Workgroup:Container: Difference between revisions

From NixOS Wiki
imported>Profpatsch
add hocker
old source is 404, new source is different, not a Dockerfile
 
(10 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{outdated|Other than site-wide fixes, this page has not seen recent updates.}}
We are interested in directly building (minimal) OCI containers from the nixpkgs ecosystem.
We are interested in directly building (minimal) OCI containers from the nixpkgs ecosystem.


Line 5: Line 6:
* [[User:Profpatsch|Profpatsch]]
* [[User:Profpatsch|Profpatsch]]
* [[User:nlewo|Lewo]]
* [[User:nlewo|Lewo]]
* [[User:moretea|MoreTea]]


== Tooling ==
== Tooling ==
Line 14: Line 16:
** [https://github.com/opencontainers/image-tools image-tools]: tools for working with the image-spec
** [https://github.com/opencontainers/image-tools image-tools]: tools for working with the image-spec
** [https://github.com/opencontainers/runtime-tools runtime-tools]: tools for working with the runtime-spec
** [https://github.com/opencontainers/runtime-tools runtime-tools]: tools for working with the runtime-spec
** [https://github.com/openSUSE/umoci umoci]: intends to be a complete manipulation tool for OCI images with a rootless mode
* [https://www.projectatomic.io/ projectatomic.io]
* [https://www.projectatomic.io/ projectatomic.io]
** [https://github.com/projectatomic/skopeo skopeo]: modify and inspect images on registries (nixpkgs: [https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/skopeo/default.nix skopeo])
** [https://github.com/projectatomic/skopeo skopeo]: modify and inspect images on registries (nixpkgs: [https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/skopeo/default.nix skopeo])
Line 23: Line 26:
** [https://github.com/awakesecurity/hocker hocker]: fetch from docker (v2) registry and generate nix derivations
** [https://github.com/awakesecurity/hocker hocker]: fetch from docker (v2) registry and generate nix derivations


== Work In Progress ==
== Nix images ==
 
There are a few images that contain Nix with various trade-offs:
 
* [https://hub.docker.com/r/nixos/nix/ nixos/nix] ([https://github.com/NixOS/nix/blob/master/docker.nix source]) - 200 MB - Official images based on <code>pkgs.dockerTools</code>, updated automatically.
* [https://hub.docker.com/u/nixpkgs u/nixpkgs] - ([https://github.com/nix-community/docker-nixpkgs source]) - [https://github.com/nix-community/docker-nixpkgs#list-of-images various] docker images from nixpkgs, updated daily.
* [https://hub.docker.com/r/lnl7/nix/ lnl7/nix/] ([https://github.com/LnL7/nix-docker source]) - 57 MB - Images built out of a Nix derivation.
 
== Interesting threads ==


* Add legacy Docker image support in Skopeo
* https://github.com/projectatomic/buildah/issues/386: about rootless support


nixpkgs.dockerTools.pullImage boots a VM to pull the image by using the Docker daemon. Skopeo could do this but it produces images that are not compatible with the Docker legacy format. The consequence is some NixOS tests are failing and it breaks some NixOS user scripts [https://github.com/containers/image/pull/370 skopeo PR].
== Work In Progress ==


* Use DigestID instead of image tag to pull images (tag is mutable)
* Improve image storage in the Nix store
https://github.com/projectatomic/skopeo/issues/481


Will be implemented when Skopeo is used to pull images


== Projects ==
== Projects ==
Line 43: Line 54:
A basic (pretty messy) [https://gitlab.techcultivation.org/sangha/sangha-deployment/blob/2f3877e71ea7a9a2c3cf03d4fc88931b90cad6b7/containers/postgres.nix postgres] image is already done, complete with in-build setup of a mock database. The resulting image is smaller than the “official” one in the docker registry, only uses nixpkgs-native dependencies and only contains the most minimal filetree needed to run the postgres binary.
A basic (pretty messy) [https://gitlab.techcultivation.org/sangha/sangha-deployment/blob/2f3877e71ea7a9a2c3cf03d4fc88931b90cad6b7/containers/postgres.nix postgres] image is already done, complete with in-build setup of a mock database. The resulting image is smaller than the “official” one in the docker registry, only uses nixpkgs-native dependencies and only contains the most minimal filetree needed to run the postgres binary.


Still to do: rabbitmq, frontend code, api, refactor, various others.
Still to do: [https://gitlab.techcultivation.org/sangha/sangha-deployment/blob/master/containers/rabbitmq.nix rabbitmq], frontend code, api, refactor, various others.


— [[User:Profpatsch|Profpatsch]] ([[User talk:Profpatsch|talk]]) 02:47, 10 February 2018 (UTC)
— [[User:Profpatsch|Profpatsch]] ([[User talk:Profpatsch|talk]]) 02:47, 10 February 2018 (UTC)
[[Category:Container]]

Latest revision as of 19:19, 14 September 2024

We are interested in directly building (minimal) OCI containers from the nixpkgs ecosystem.

People

Tooling

Nix images

There are a few images that contain Nix with various trade-offs:

Interesting threads

Work In Progress

  • Improve image storage in the Nix store

https://github.com/projectatomic/skopeo/issues/481


Projects

Self-Hosted, Minimal Docker/OSI Images

For our platform at Techcultivation we want to generate docker images for all parts of our system. Those images should come in two flavors, development (to quickly spin up local test services, with mock data) and deployment (secure/production-ready). We chose to generate these images purely out of nixpkgs code, so no binary (base) images have to be included.

The current version of the deployment code can be found on our Gitlab.

A basic (pretty messy) postgres image is already done, complete with in-build setup of a mock database. The resulting image is smaller than the “official” one in the docker registry, only uses nixpkgs-native dependencies and only contains the most minimal filetree needed to run the postgres binary.

Still to do: rabbitmq, frontend code, api, refactor, various others.

Profpatsch (talk) 02:47, 10 February 2018 (UTC)