Edit history

Earlier versions of Publish an experimental LXC rootfs artifact, newest first.

Current version | Edited by Rex
Changes
The goal is not to replace Docker, only to provide an additional deployment option for Proxmox, Incus/LXD and other LXC users.Removed: ### ChecksRemoved: Removed: - ☑ I searched existing discussions.Removed:
Show

Publish an experimental LXC rootfs artifact

Problem

I run Fluxer on Proxmox, where using Docker inside a VM or LXC adds unnecessary complexity. A native LXC is much easier to manage, back up and integrate with ZFS. This would also be useful for people using LXC outside of Proxmox.

Proposal

Could the release workflow also generate a single LXC-compatible .tar.zst rootfs containing the full Fluxer stack? I am not asking for official support, only an automatically generated experimental artifact alongside the existing Docker images.

Notes

It could be clearly marked as experimental and unsupported. The goal is not to replace Docker, only to provide an additional deployment option for Proxmox, Incus/LXD and other LXC users.
Original by Rex
Show

Publish an experimental LXC rootfs artifact

Problem

I run Fluxer on Proxmox, where using Docker inside a VM or LXC adds unnecessary complexity. A native LXC is much easier to manage, back up and integrate with ZFS. This would also be useful for people using LXC outside of Proxmox.

Proposal

Could the release workflow also generate a single LXC-compatible .tar.zst rootfs containing the full Fluxer stack? I am not asking for official support, only an automatically generated experimental artifact alongside the existing Docker images.

Notes

It could be clearly marked as experimental and unsupported. The goal is not to replace Docker, only to provide an additional deployment option for Proxmox, Incus/LXD and other LXC users.

Checks

  • ☑ I searched existing discussions.