WIP: Compartimentalise CI using Docker #393
No reviewers
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#393
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Niols:ci-in-docker"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
part of #362.
nixoslabelit looks like making the image we want has been done before. to ensure the runner can see the image, i think our options seem:
icewind1991/nix-runnerbuildImagethat docker can already see itvirtualisation.oci-containers.containerssome hook topushto e.g. forgejo's registry after the above create it?some TF crapkiara referenced this pull request2025-06-19 08:32:07 +02:00
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?
@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.
nixops4 apply testerror:proxmox-qemu-vm.nix was imported into nixops4Resource instead of nixos#431Pull request closed