poe-stash-indexer VS muslrust

Here is a pipeline when the cache was missed due to GitHub cache eviction, so a fresh build. Here is a pipeline when the cache was hit.

Wrt #2: I use VSCodium with manually installed extensions as well. In my shell.nix I have cargo and rusr-analyzer as build inputs and I start the editor from within the nix shell via nix-shell && code . which works fine. Here is my config , but maybe I misunderstood your problem.

IIRC the single most effective thing for my CI setup was using mold as a linker. There are good resources on the web on how to set that up. This is what I did for my docker builds.

as mentioned in my post a few weeks ago, I am running my public trade API service for Sentinel league as well.

All API documentation and further info can be found on this GitHub repository. I plan on running this during the upcoming challenge leagues as well.

I also use alpine to run my app, maybe this Dockerfile helps you link.

Already some good comments there, but here is how I did it recently.

That's isn't true, one can make fully independent static binary in rust

The winning combo that I found works great is a multistage build, using clux/muslrust to build the dependencies + the binary itself, then using a scratch image as the final stage. Depending on the complexity, the statically linked images I use range from ~9MB to ~22MB. The 9MB image was ported from an existing container that was dynamically linked, and if I remember right, the image was in the ~70-80MB range using debian:buster-slim as the final stage.

muslrust: seems to be active last commit on Oct 2, 2021. But what is the difference compared to the one above?

Oh, I remember that I use https://github.com/clux/muslrust and is there what the bug is triggered. Weirdly, running it locally not show it.

After a lot of searching I came across a Docker image which provides a clean environment for building Rust linked against musl libc. It includes curl, pq, sqlite3, and zlib, but the main one I needed was OpenSSL. This container image solved my problem and I can run using Docker locally as well as in the GitHub Action build workflow.