musl-cross-make VS graylog-docker

I've done the same alpine trick for static binaries but may I introduce you to musl-cross-make?

https://github.com/richfelker/musl-cross-make

Just burned out static toolchains that make me static binaries for all architectures gcc supports. Much like musl.cc but they suggest building your own and I do.

I use these toolchains on debian (/ anywhere a non-ancient linux kernel runs) to make static binaries, you can too!

Python obviously isn't 14kb because its code is divided into hundreds of shared object files. So the way I like to measure things is using static executable size, using tools like https://github.com/jart/cosmopolitan or https://github.com/richfelker/musl-cross-make of which you'll find a static build in the cosmo repo. For example, here's the technique I used to build TinyLISP was something like this:

I have a different issue with ring. This is on a custom Cortex A9 board at work. For most depedencies I can get compilation working fine with armv7-unknown-linux-musleabihf. I was able to build the cross compiler using https://github.com/richfelker/musl-cross-make , adding

A bit off topic, I hope someday GCC's build system gets overhauled. A huge advantage of LLVM is that it is quite easier to rebuild the runtime libraries without rebuilding the compiler. With GCC that's a pain, unless one takes the time to re-package GCC very carefully like https://github.com/richfelker/musl-cross-make and https://exherbo.org/.

Maybe getting some new GCC devs in there with projects like this would help with that?

version: '3' services: # MongoDB: https://hub.docker.com/_/mongo/ mongo: image: mongo:5.0.13 networks: - graylog # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/docker.html elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 environment: - http.host=0.0.0.0 - transport.host=localhost - network.host=0.0.0.0 - "ES_JAVA_OPTS=-Dlog4j2.formatMsgNoLookups=true -Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 deploy: resources: limits: memory: 1g networks: - graylog # Graylog: https://hub.docker.com/r/graylog/graylog/ graylog: image: graylog/graylog:5.0 environment: # CHANGE ME (must be at least 16 characters)! - GRAYLOG_PASSWORD_SECRET=somepasswordpepper # Password: admin - GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918 - GRAYLOG_HTTP_EXTERNAL_URI=http://127.0.0.1:9000/ entrypoint: /usr/bin/tini -- wait-for-it elasticsearch:9200 -- /docker-entrypoint.sh networks: - graylog restart: always depends_on: - mongo - elasticsearch ports: # Graylog web interface and REST API - 9000:9000 # Syslog TCP - 514:514 # Syslog UDP - 514:514/udp # GELF TCP - 12201:12201 # GELF UDP - 12201:12201/udp networks: graylog: driver: bridge

So I surveyed docker images in my personal use:

Postgres (Docker provided - https://hub.docker.com/_/postgres): Debian (with alternates for alpine or other debian versions)

Jellyfin (Developer provided - https://github.com/jellyfin/jellyfin/blob/master/Dockerfile): They use an alpine build step but the final distributed image is debian

Calibre-Web (Linuxserver provided - https://github.com/linuxserver/docker-calibre-web/blob/maste...): Ubuntu

Graylog (Developer provided - https://github.com/Graylog2/graylog-docker/blob/4.2/docker/o...): Debian

Vaultwarden (Developer provided - https://github.com/dani-garcia/vaultwarden/blob/main/docker/...): Debian (with alpine alternate available)

For professional use, our company mandates all images used are built off a common base image, which is Ubuntu based (my previous employer was similar, but used a Red Hat based image).

The ROOT_PASSWORD_SHA2 environment variable is only for the web interface. The underlying container is built on an openjdk Debian Bullseye image, as you can see here: https://github.com/Graylog2/graylog-docker/blob/4.2/docker/enterprise/Dockerfile