In the first part, we saw how to create a basic Rust API with a In this part, let's see how to containerize our app!<\/p>\n\n Since AWS App Runner is a fully managed container application service, we definitely need a container!<\/p>\n\n In this section, we will see how to build that container thanks to A Let's start with The first line describes the base image that we want to use, here the official This is really convenient since we don't have to install Then we define the current working directory, here Then we copy our sources ( Finally we build our API directly inside the container, in release mode, to be sure to have a production-ready binary.<\/p>\n\n Great, we now have our binary ready in our image!<\/p>\n\n But wait, we also have It was convenient to use the official We can specify a base image to build and another one to run! That's exactly what we want!<\/p>\n\n The idea here is to have the smallest possible image so the cold start would be extremely fast. That's why we are going to use a Those images are built by Google and contain almost nothing: no Let's modify our Dockerfile: Here we name our first image Our runtime image is just the Let's finally build it with Let's check for our image size: 20.1MB!!! \ud83e\udd2f Extremely small!<\/strong><\/p>\n\n Woot woot! We now have a ready to deploy container!<\/p>\n\n Before deploying, let's make sure everything looks fine by running it locally and calling our You can run your newly built docker image with: You can check that your container is up and running with: Now you can curl the endpoint: Awesome! \ud83c\udf89<\/p>\n\n Our container is now ready to be used by AWS App Runner.<\/strong> <\/p>\n\n See you next week for the final episode of this series to deploy it!<\/p>\n\n Like this content? Consider following me for more!<\/strong><\/p>\n\n A question? Feel free to use the comment section \u2b07\ufe0f<\/p>\n\n You can find me on LinkedIn<\/a>, YouTube<\/a> and Twitter<\/a>!<\/p>\n\n"},{"title":"Rust on AWS App Runner - Part1","pubDate":"Mon, 21 Aug 2023 14:36:51 +0000","link":"https:\/\/dev.to\/aws-builders\/rust-on-aws-app-runner-part1-4hpp","guid":"https:\/\/dev.to\/aws-builders\/rust-on-aws-app-runner-part1-4hpp","description":" Hey hey hey \ud83c\udf55!<\/p>\n\n Over the past few months, I've been advocating for Rust on AWS Lambda a lot!<\/p>\n\n Here is a quick recap in case you missed it!<\/p>\n\n By the way, we're almost at 256 \u2b50\ufe0f which is \ud83e\udd2f for a side project! I'm sure we can do it!<\/p>\n\nGET \/pizza<\/code> endpoint to retrieve the list of pizza.<\/p>\n\n\n \n \n Let's create our container\n<\/h2>\n\n
Docker<\/code> using a Dockerfile<\/code>.<\/p>\n\nDockerfile<\/code> is a text file that contains all the commands needed to build our container, it's often compared to a recipe.<\/p>\n\n\n \n \n Rust as the base image\n<\/h2>\n\n
\n<\/p>\n\nFROM<\/span> rust:slim-bullseye<\/span>\nWORKDIR<\/span> \/app<\/span>\nCOPY<\/span> .\/ \/app<\/span>\nRUN <\/span>cargo build --release<\/span>\n<\/code><\/pre>\n\n<\/div>\n\n\n\nrust<\/code> one. <\/p>\n\nrust<\/code> or cargo<\/code>: both are already installed in this base image.<\/p>\n\n\/app<\/code><\/p>\n\nsrc<\/code> + Cargo.toml<\/code> + Cargo.lock<\/code>) into the container.<\/p>\n\nrust<\/code>, cargo<\/code> and a bunch of useless tools at runtime. <\/p>\n\nrust<\/code> image to build<\/strong>, but we don't need it anymore for the runtime<\/strong>. Fortunately, Docker supports multi stage builds<\/strong>.<\/p>\n\n\n \n \n Multi-stage builds\n<\/h2>\n\n
distroless<\/code> base image.<\/p>\n\nbash<\/code>, no ssh<\/code>, no utility tools which makes the image extremely small.<\/p>\n\n
\n<\/p>\n\nFROM<\/span> <\/span>rust:slim-bullseye<\/span> <\/span>AS<\/span> <\/span>BUILD<\/span>\nCOPY<\/span> .\/ \/app<\/span>\nRUN <\/span>cargo build --release<\/span>\n\nFROM<\/span> gcr.io\/distroless\/cc-debian10<\/span>\nCOPY<\/span> --from=BUILD \/app\/target\/release\/app-runner-rust \/ <\/span>\nCMD<\/span> [\".\/app-runner-rust\"]<\/span>\n<\/code><\/pre>\n\n<\/div>\n\n\n\nBUILD<\/code> so we can reference that later. Then from the distroless image, we copy our binary from the BUILD<\/code> image! Super convenient! I love Docker :D<\/p>\n\ndistroless base image<\/code> + rust binary<\/code><\/p>\n\ndocker build . -t maxday\/app-runner<\/code><\/p>\n\ndocker images | grep maxday\/app-runner<\/code>
\n<\/p>\n\ndocker images | grep <\/span>maxday\/app-runner\nmaxday\/app-runner latest e278afc78403 3 minutes ago 20.1MB\n<\/code><\/pre>\n\n<\/div>\n\n\n\n\n \n \n Local test\n<\/h2>\n\n
GET \/pizza<\/code> endpoint.<\/p>\n\n
\ndocker run -d -p 8080:8080 maxday\/app-runner<\/code><\/p>\n\n\n
-d<\/code> means detached<\/code> so the container runs in the background<\/li>\n-p 8080:8080<\/code> means that you're bridging the host port 8080 to the container port 8080.<\/li>\n<\/ul>\n\n
\ndocker ps<\/code>
\n<\/p>\n\ndocker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\ne5d8978ee6ee maxday\/app-runner \".\/app-runner-rust\"<\/span> 53 seconds ago Up 53 seconds 0.0.0.0:8080->8080\/tcp pedantic_kare\n<\/code><\/pre>\n\n<\/div>\n\n\n\n
\ncurl http:\/\/localhost:8080\/pizza<\/code>
\n<\/p>\n\ncurl localhost:8080\/pizza\n[{<\/span>\"name\"<\/span>:\"Margherita\"<\/span>,\"toppings\"<\/span>:[\"tomato\"<\/span>,\"fior di latte\"<\/span>]<\/span>,\"price\"<\/span>:10}<\/span>,{<\/span>\"name\"<\/span>:\"Veggie\"<\/span>,\"toppings\"<\/span>:[\"green peppers\"<\/span>,\"onion\"<\/span>,\"mushrooms\"<\/span>]<\/span>,\"price\"<\/span>:12}]<\/span>\n<\/code><\/pre>\n\n<\/div>\n\n\n\n\n
![\"file](\"https:\/\/res.cloudinary.com\/practicaldev\/image\/fetch\/s--AMbpPlqn--\/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800\/https:\/\/dev-to-uploads.s3.amazonaws.com\/uploads\/articles\/43q551m441gvqrunlczx.png\")
<\/a><\/p>\n