Containerize Redwood Sides with Docker Compose

pi0neerpat · April 15, 2022, 7:26pm

Ok ROUND 2 fight with docker size. I got the image down to 1.15GB from ~2GB. I documented my journey here:

github.com/pi0neerpat/redwood-release-devops-example

Docker size reduction

pi0neerpat:dev ← pi0neerpat:docker-size-reduction

opened 05:34AM - 14 Apr 22 UTC

pi0neerpat

+107 -38

This PR is focused on reducing the /api image size. It has been reduced from ~2G…B to **1.17GB** ### Changes - Using --production flag to skip dev dependencies saved a ton of space! (THIS IS A MUST) - `yarn cache clean` saved a ton of space! (THIS IS A MUST) - Added `lerna`, which is required to use the local `/packages` dependencies. This is working great now. - `yarn global add @redwoodjs/api-server @redwoodjs/internal ` to serve the api from bin ### Discussion > If you do a multi-stage dockerfile, you can build everything, run migrations, then just grab the dist directories. At that point all you need is the api-server package. You can run the server as a bin via: yarn rw-server [side] > -David's super optimistic suggestion - I was not able to just grab the dist directories, due to missing deps for `graphql-server` at runtime. I ran out of time to continue down this rabbit hole. - I could not use node-alpine because I am use packages like canvas to render images in `/api`. This causes `node-gyp` and `python` errors. From a DevX point of view I believe recommending alpine is not the right path, or it should be heavily documented that both options be suggested.