WIP: Compartimentalise CI using Docker #393

Closed
Niols wants to merge 1 commit from Niols:ci-in-docker into main
Owner

part of #362.

part of #362.
Switch all CI jobs to nixos label
Some checks failed
/ check-pre-commit (pull_request) Failing after 1m13s
/ check-data-model (pull_request) Failing after 1m8s
/ check-peertube (pull_request) Failing after 17s
/ check-panel (pull_request) Failing after 5s
/ check-deployment-basic (pull_request) Failing after 5s
/ check-deployment-cli (pull_request) Failing after 4s
/ check-deployment-panel (pull_request) Failing after 4s
cb0379664e
Owner

it looks like making the image we want has been done before. to ensure the runner can see the image, i think our options seem:

  • use a manual push, not unlike their existing icewind1991/nix-runner
  • see if using buildImage that docker can already see it
  • as above but with virtualisation.oci-containers.containers
  • some hook to push to e.g. forgejo's registry after the above create it?
  • some TF crap
it looks like making the image we want [has been done before](https://icewind.nl/entry/gitea-actions-nix/). to ensure the runner can see the image, i think our options seem: - use a manual push, not unlike their existing [`icewind1991/nix-runner`](https://hub.docker.com/r/icewind1991/nix-runner) - see if using `buildImage` that docker can already see it - as above but with `virtualisation.oci-containers.containers` - ~~some hook to `push` to e.g. [forgejo's registry](https://docs.gitea.com/usage/packages/container) after the above create it?~~ - ~~some [TF crap](https://registry.terraform.io/providers/kreuzwerker/docker/latest/docs/resources/registry_image)~~
kiara added this to the Fediversity project 2025-06-19 13:31:24 +02:00
Author
Owner

We can probably add a docker image to a NixOS machine, no? Then we wouldn't need to add it to any registry, because it would always be there in the cache?

We can probably add a docker image to a NixOS machine, no? Then we wouldn't need to add it to any registry, because it would always be there in the cache?
Owner

@Niols that sounds better yes. i guess i was stuck thinking the container way, whereas for nixos purposes the function of such a registry i guess may just be assumed by a nix cache, given any of our consumers (so far 1) use nix.

@Niols that sounds better yes. i guess i was stuck thinking the container way, whereas for nixos purposes the function of such a registry i guess may just be assumed by a nix cache, given any of our consumers (so far 1) use nix.
Niols closed this pull request 2025-07-02 14:43:24 +02:00
Some checks are pending
/ check-pre-commit (pull_request) Failing after 1m13s
Required
Details
/ check-data-model (pull_request) Failing after 1m8s
Required
Details
/ check-peertube (pull_request) Failing after 17s
Required
Details
/ check-panel (pull_request) Failing after 5s
Required
Details
/ check-deployment-basic (pull_request) Failing after 5s
Required
Details
/ check-deployment-cli (pull_request) Failing after 4s
Required
Details
/ check-deployment-panel (pull_request) Failing after 4s
Required
Details
/ check-resources (pull_request)
Required
/ check-mastodon (pull_request)
Required

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: fediversity/fediversity#393
No description provided.