Post AkwRAUlFSOtayrtsps by dalias@hachyderm.io
 (DIR) More posts by dalias@hachyderm.io
 (DIR) Post #AkvshJE5rpDsMoIuLw by aphyr@woof.group
       2024-08-13T18:18:58Z
       
       3 likes, 2 repeats
       
       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.
       
 (DIR) Post #AkvshL9CiyV4KE220e by aphyr@woof.group
       2024-08-13T18:20:59Z
       
       1 likes, 0 repeats
       
       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
       
 (DIR) Post #AkwGDJkZkivWCijG5o by lain@lain.com
       2024-08-13T22:54:16.608893Z
       
       0 likes, 0 repeats
       
       @aphyr just install docker inside your lxc
       
 (DIR) Post #AkwQu1fbqgj07iPSnQ by dalias@hachyderm.io
       2024-08-13T19:28:53Z
       
       1 likes, 0 repeats
       
       @arclight @aphyr Hot take: derivatives of GPL works distributed so that they're unbuildable without some awful undocumented container setup are infringing because build scripts are part of the mandated definition of source.
       
 (DIR) Post #AkwRARQvpTrUezN7Fg by owen@mastodon.transneptune.net
       2024-08-13T18:44:32Z
       
       0 likes, 0 repeats
       
       @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).
       
 (DIR) Post #AkwRASIScSgDL0Prge by dalias@hachyderm.io
       2024-08-13T19:26:40Z
       
       0 likes, 0 repeats
       
       @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". 🤬
       
 (DIR) Post #AkwRAT3xlqg3iKdnjE by owen@mastodon.transneptune.net
       2024-08-13T20:24:12Z
       
       0 likes, 0 repeats
       
       @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.
       
 (DIR) Post #AkwRATwuTYd6SkLgNE by srtcd424@mas.to
       2024-08-13T22:30:36Z
       
       0 likes, 0 repeats
       
       @owenFor 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
       
 (DIR) Post #AkwRAUlFSOtayrtsps by dalias@hachyderm.io
       2024-08-13T22:34:45Z
       
       0 likes, 0 repeats
       
       @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.