LXC container deployment #724
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#289 key features improving user experience supported
fediversity/fediversity
#833 unit-tested functionality integrated in deployment pipelines
fediversity/fediversity
#954 demo env broken
fediversity/fediversity
Reference
fediversity/fediversity#724
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
our hypervisor deployment currently deploys to VMs, see test
deployment-tf-proxmox.we could instead just use the (lighter-weight) containers instead, which are similarly supported and do not need their own kernel.
implementation notes
nspawn- less aimed at hardening / multi-tenancy?systemd-nspawn(no UI or TF?)proxmox-nixos(TF)incus(leaner, TF)OCI(would imply modular services, see #598)nimikubernetes (#598)pve-qemubuild fails with OOM #849container deploymentto LXC container deploymentfwiw docker switched away from LXC - long-run we probably should further investigate OCI (c.f. #598 / #620)
closed in #1205, for which we deployed a hypervisor to
dev1(192.168.51.101)