lambda-layer-sharp VS strapi-plugin-local-image-sharp

This plugin is used for all our AWS Lambda deployments, using a wide range of Node modules, some with more quirks than others. We use it together with Lambda Layer Sharp and Chrome AWS Lambda.

FROM node:18-alpine3.18 AS build_image # Installing libvips-dev for sharp Compatability RUN apk update && apk add --upgrade --no-cache vips-dev build-base fftw-dev gcc autoconf g++ make libc6-compat zlib-dev libpng-dev nasm bash --repository https://alpine.global.ssl.fastly.net/alpine/v3.18/community/ # Set working directory WORKDIR /opt # Resolve node_modules for caching COPY package.json yarn.lock ./ # Install dependencies RUN yarn install # Copy all for build and release cache if package.json update COPY . . ENV NODE_ENV=production RUN yarn build # Remove unnecessary files from node_modules - https://github.com/tj/node-prune RUN wget https://gobinaries.com/tj/node-prune --output-document - | /bin/sh && node-prune #------------------------------------------------------------------------------------ # Create a new namespace for the final Docker Image FROM node:18-alpine3.18 # Installing openssh RUN apk --no-cache update && apk add openssh # Installing vips-dev (https://www.libvips.org/) - https://github.com/strapi-community/strapi-plugin-local-image-sharp RUN apk add vips-dev # Set working directory WORKDIR /opt/app # Only copy your source code without the system file COPY --from=build_image /opt ./ EXPOSE 1337 ENV NODE_ENV=production ENV STRAPI_LOG_LEVEL=debug CMD ["yarn", "start"]