Railway Rocket Template Won't Deploy OpenSSL?
Repo to reproduce: https://github.com/get-river/geoip-microservice
The build fails with the following error. I have no idea how to debug or resolve this since its a docker container / railway Nix Packs build...
Any suggestions gang?
GitHub
GitHub - get-river/geoip-microservice
Contribute to get-river/geoip-microservice development by creating an account on GitHub.
13 Replies
Project ID:
N/Afull build logs please https://bookmarklets.up.railway.app/log-downloader/
getting now
this is from the most recent build where I tried to manually specify cargo build and cargo run
let me get the one where I tried deploying with all the defaults from the template...
this would be something you added to the crates that needs openssl
?
so adding this depdency is somehow causing the build error?
i guess I just don't understand why it runs fine locally, do I need to manually add openssl into my Cargo.toml?
also here is the build logs with all of the tempalte defaults instead of manually specifying a build and run command
I think there is a rust crate that does add openssl, so for sure look into that
@Brody so I'm pretty sure this is a nix pax issue / an issue with the docker file that railway is generating for my project. Is there any way to edit that docker file that is running in this build?
I tested my project on all 3 operating systems and its working by default with no additional config
It only fails to build on railway
even when I use a blank railway project template and try to build / run through cargo build
I can also just switch to golang or something haha
might just work out of the box 😂 rust is dumb sometimes
well yes and no to it being a nixpacks issue, ideally nixpacks would automatically detect the specific crate you are using that needs openssl and add the system dependency automatically, but at this time it doesn't.
I have seen people solve this by installing some openssl crate as I recommend you try above.
and while you can't modify the dockerfile nixpacks generates directly, you can modify the build plan with a nixpacks.toml file, with this you can get nixpacks to install nix packages or apt packages https://nixpacks.com/docs/configuration/file