"We failed to create a container for this image."
lukenewman
PROOP

2 years ago

Got a Dockerfile that builds fine on my local machine, but for some reason the container can't be built / uploaded through Railway. Dockerfile is pretty simple:

FROM rust:1.74-slim-buster
RUN apt-get update && apt-get install -y openssl pkg-config libssl-dev clang libclang-dev
WORKDIR /app
COPY . .
RUN cargo build
ENTRYPOINT ["cargo run"]

Please let me know what other info may be helpful!

Thanks in advance!

Solved

0 Replies

lukenewman
PROOP

2 years ago

d462d0b1-509b-4747-9990-ee5a56c78771


vin
PRO

2 years ago

@luke this can happen from time to time. Give it a bit and try to do another deploy, and it should work


Status changed to Solved Railway about 2 years ago


brody
EMPLOYEE

2 years ago

what vin said + you should build in release mode, then your entrypoint should be the binary file that was previously built


lukenewman
PROOP

2 years ago

holy shit you guys just now seeing y'all's response -- issue had resolved itself but @Brody thank you so much for pointing that out you just sped up execution times significantly hahahaha


brody
EMPLOYEE

2 years ago

haha no problem


callmefredcom
PRO

2 years ago

I'm also experiencing "We failed to create a container for this image".
What does this mean to "build in release mode"?..


callmefredcom
PRO

2 years ago

update, it worked… I just published a minor edit and it got unstuck.


Loading...