Conversation

Notices

1. Embed this notice
   Esprit de Vore (aphyr@woof.group)'s status on Wednesday, 14-Aug-2024 05:25:29 JST Esprit de Vore

   I am begging software projects to release programs as tarballs or plain old static binaries. I don't know what a Helm chart is. I am not installing an entire Kubernetes cluster. Docker breaks LXC and firewalls and is constantly breaking for mysterious reasons. I would rather submit myself to hours of `./configure && make && make install` frustration than try to hack through the endless hellscape of containerized deployment systems.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Kit Rhett Aultman repeated this.
   • Embed this notice
     on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ (lain@lain.com)'s status on Wednesday, 14-Aug-2024 07:54:20 JST on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ

     in reply to
     @aphyr just install docker inside your lxc
   • Embed this notice
     Steven Reed (srtcd424@mas.to)'s status on Wednesday, 14-Aug-2024 09:56:56 JST Steven Reed

     in reply to

     • Rich Felker
     • Owen (spoopy aspect)

     @owen
     For the nss case at least, nscd or nsncd work around that - its how nixos deals with it's own special problems in this area. (FWIW, nix might be another solution to the OP's 'i don't want to deal with containers' problem)
     @dalias

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 14-Aug-2024 09:56:56 JST Rich Felker

     in reply to

     • Owen (spoopy aspect)
     • Steven Reed

     @srtcd424 @owen Not really. In #musl we honor nscd for user/group db because the protocol is workable, we aim not to NIH things, and it gives custom db backend support. But not the nss hostname stuff. It lacks sufficient capability (hosts backend can't do scope ids for link local addresses) and it has broken fallback logic that doesn't treat nonexistence safely, and DNS protocol already provides a more capable way to do custom backend if needed.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 14-Aug-2024 09:57:00 JST Rich Felker

     in reply to

     • Owen (spoopy aspect)

     @owen @aphyr If it's static it doesn't care about the host libc.

     Lots of folks lie tho and say static when they mean "static except glibc and whatever other part of our base system we assume is the same as yours". 🤬

   • Embed this notice
     Owen (spoopy aspect) (owen@mastodon.transneptune.net)'s status on Wednesday, 14-Aug-2024 09:57:00 JST Owen (spoopy aspect)

     in reply to

     • Rich Felker

     @dalias Given the existence of services like nss and pam, I'm not sure statically linking libc is universally a good idea either. Discovering that one program disagrees with the rest of my system about how user IDs map to user names, or about how hostnames map to addresses, is intensely frustrating.

   • Embed this notice
     Owen (spoopy aspect) (owen@mastodon.transneptune.net)'s status on Wednesday, 14-Aug-2024 09:57:04 JST Owen (spoopy aspect)

     in reply to

     @aphyr I am legitimately not sure where I am more annoyed by "here is our helm chart, good luck" or "here is a single static binary for you to run (assuming your system uses the same libc as ours) (assuming you trust blobs)" (looking at you here hashicorp).

   • Embed this notice
     Esprit de Vore (aphyr@woof.group)'s status on Wednesday, 14-Aug-2024 10:12:36 JST Esprit de Vore

     in reply to

     if you release a .deb that installs cleanly on stock debian stable I will kiss you sweetly while whispering words of affirmation into your ears

     Kit Rhett Aultman repeated this.
   • Embed this notice
     don Elías (como los buses) 🥨 (donelias@mastodon.cr)'s status on Wednesday, 14-Aug-2024 10:13:18 JST don Elías (como los buses) 🥨

     in reply to

     @aphyr

     A .deb package, oh yeah