News for hackers. Stuff that matters.
Re:Setting Up a Software Development Environment on Alpine L... by erikw on Tuesday March 19, 2019 @08:30PM (#19437657)
I like to set up mini dev environments in Alpine Docker containers when I'm testing or trying out a new stack, and for the most part really like this pattern. That said, I run into a lot of issues that I think are musl related. The best part though is that when I finally get things working, everything is documented nice and declaratively between the Dockerfile and the docker-compose file, so I can come back to it later or clone it for a different project and it just works.
Re:Setting Up a Software Development Environment on Alpine L... by sandov on Tuesday March 19, 2019 @10:16PM (#19438279)
Pardon my ignorance, but what's the nature of these musl-related issues? Is it because some programs or libraries use glibc specific-features/bugs? Or is it something else? Does glibc have their own non-standard functions?
Re:Setting Up a Software Development Environment on Alpine L... by tyingq on Tuesday March 19, 2019 @10:23PM (#19438324)
Pre built jvm binaries that are dynamically linked to glibc are an example.

"At present, some glibc-linked shared libraries can be loaded with musl, but all but the simplest glibc-linked applications will fail if musl is dropped-in in place of /lib/ld-linux.so.2"

https://www.musl-libc.org/faq.html

Some of the differences are listed here: https://wiki.musl-libc.org/functional-differences-from-glibc...

Re:Setting Up a Software Development Environment on Alpine L... by kristianp on Wednesday March 20, 2019 @04:26AM (#19440056)
That reminded me that I noticed from the java 12 link on the front page, that they mention early access builds of java 13 for alpine. https://jdk.java.net/13/