7 ms·

Debian is a bad choice if you want to package go applications (or rust apps, for that matter). Debian requires that all those little static dependencies be indi

Debian is a bad choice if you want to package go applications (or rust apps, for that matter). Debian requires that all those little static dependencies be individually packaged. Common container software like lxd, podman, and umoci are not found in Debian. The following distributions package LXD (that I know of): * Void Linux * Alpine Linux * Arch Linux * Gentoo Some of those are more suitable for production installs than others, but if you know what you are doing and manage your deployments well, all of them could work.

rawoke083600 7y ago
Ahh Gentoo :) I once build-from-source think it was called stage-1 install on a SBC(Single Board Computer) 486DX. I compiled well over 4 days :D
willtim 7y ago
I would add NixOS to that list. Especially if you value rolling back upgrades or pinning package versions.
- CameronNemo 7y ago
  I was not aware. Too late to edit now, but that is indeed a great option! Rolling release is a bit ambitious for a hyperlink without nixos like features.
yrro 7y ago
Podman is in the NEW queue, and debs can be built from the packaging repo in the meantime., FYI.
- CameronNemo 7y ago
  Thanks for the info! Good to hear.
francislavoie 7y ago
Do you happen to know _why_ Debian decided to require that for Go projects? It's so absurdly complicated. I've been looking into .deb packaging for Caddy but it really feels like they require us to jump through too many hoops to make it happen. I'd much rather just ship a prebuilt binary.
- tribaal 7y ago
  I would love a deb-packaged Caddy as well :(
  - francislavoie 7y ago
    You'll be happy to know Caddy will have a deb package in the next release (albeit not part of official debian repos), see https://github.com/caddyserver/caddy/pull/3309 https://github.com/caddyserver/caddy/pull/3309
- Foxboron 7y ago
  >It's so absurdly complicated. Security. Dynamically linking stuff is always going to be better than statically linking. Do you trust upstream to keep track of security issues and rebuild in the absurd dependency tree that is Golang software? Or the multi-year old effort which is the current Debian security team? The reason why it's absurdly complicated is solely on the Golang team, not Debian.
Foxboron 7y ago
Funny. I have been working on a blogpost detailing the silly things I encountered while packaging LXD properly for Arch Linux. Should probably finish it up one of these days.

rawoke083600 7y ago

Ahh Gentoo :) I once build-from-source think it was called stage-1 install on a SBC(Single Board Computer) 486DX. I compiled well over 4 days :D

willtim 7y ago

I would add NixOS to that list. Especially if you value rolling back upgrades or pinning package versions.

CameronNemo 7y ago
I was not aware. Too late to edit now, but that is indeed a great option! Rolling release is a bit ambitious for a hyperlink without nixos like features.

yrro 7y ago

Podman is in the NEW queue, and debs can be built from the packaging repo in the meantime., FYI.

CameronNemo 7y ago
Thanks for the info! Good to hear.

francislavoie 7y ago

Do you happen to know _why_ Debian decided to require that for Go projects? It's so absurdly complicated. I've been looking into .deb packaging for Caddy but it really feels like they require us to jump through too many hoops to make it happen. I'd much rather just ship a prebuilt binary.

tribaal 7y ago
I would love a deb-packaged Caddy as well :(
- francislavoie 7y ago
  You'll be happy to know Caddy will have a deb package in the next release (albeit not part of official debian repos), see https://github.com/caddyserver/caddy/pull/3309 https://github.com/caddyserver/caddy/pull/3309
Foxboron 7y ago
>It's so absurdly complicated. Security. Dynamically linking stuff is always going to be better than statically linking. Do you trust upstream to keep track of security issues and rebuild in the absurd dependency tree that is Golang software? Or the multi-year old effort which is the current Debian security team? The reason why it's absurdly complicated is solely on the Golang team, not Debian.

Foxboron 7y ago

Funny. I have been working on a blogpost detailing the silly things I encountered while packaging LXD properly for Arch Linux. Should probably finish it up one of these days.