hacc/haccfiles
8
0
Fork 1
Code Issues 1 Pull requests Projects Releases Wiki Activity

modules/containers: a hacc-specific containers module #11

Manually merged
stuebinm merged 1 commit from hacc.containers into main 2024-04-27 21:12:52 +00:00
Conversation 2 Commits 1 Files changed 10 +134 -135
stuebinm commented 2024-04-19 17:19:45 +00:00
Owner
Copy link

this started with emily pointing out to me that it's possible to generate IP addresses for containers in Nix (hence no need to worry about ever having collisions, as we had before), but then I thought, hey, while I'm at it, I can also write a little container module so we have a little less repetition in our configs in general (and a more reasonable place for our custom evalConfig than just keeping it around in flake.nix).

See the option descriptions in modules/containers.nix for further details.

Apart from giving all containers a new IP address (and also shiny new IPv6 addresses), this should be a no-op for the actual built system.

I've not deployed this yet (though afaict this should "just work"), for now it's just meant as an idea. Anyone got opinions on this?

this started with emily pointing out to me that it's possible to generate IP addresses for containers in Nix (hence no need to worry about ever having collisions, as we had before), but then I thought, hey, while I'm at it, I can also write a little container module so we have a little less repetition in our configs in general (and a more reasonable place for our custom evalConfig than just keeping it around in flake.nix). See the option descriptions in modules/containers.nix for further details. Apart from giving all containers a new IP address (and also shiny new IPv6 addresses), this should be a no-op for the actual built system. I've not deployed this yet (though afaict this should "just work"), for now it's just meant as an idea. Anyone got opinions on this?
stuebinm added 1 commit 2024-04-19 17:19:45 +00:00 
this started with emily pointing out to me that it's possible to
generate IP addresses for containers in Nix (hence no need to worry
about ever having collisions, as we had before), but then I thought,
hey, while I'm at it, I can also write a little container module so we
have a little less repetition in our configs in general (and a more
reasonable place for our custom evalConfig than just keeping it around
in flake.nix).

See the option descriptions in modules/containers.nix for further
details.

Apart from giving all containers a new IP address (and also shiny new
IPv6 addresses), this should be a no-op for the actual built system.
moira commented 2024-04-26 14:48:29 +00:00
Owner
Copy link

I think it's a good idea and makes the config easier to read/understand.
I've found nothing obviously wrong with this, so I guess, you can go ahead and test it.
Feel free to let me know, if you want any support

I think it's a good idea and makes the config easier to read/understand. I've found nothing obviously wrong with this, so I guess, you can go ahead and test it. Feel free to let me know, if you want any support
stuebinm manually merged commit f654b33a56 into main 2024-04-27 21:12:52 +00:00
stuebinm commented 2024-04-27 21:13:28 +00:00
Author
Owner
Copy link

seems to work as expected, have merged it

seems to work as expected, have merged it
stuebinm deleted branch hacc.containers 2024-04-27 21:13:31 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: hacc/haccfiles#11
No description provided.
Delete branch "hacc.containers"

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?