. ~/init/gcc && npm install && npm test. output is
$ . ~/init/gcc && npm install && npm run test Installing GCC 4.8.5... ++ curl -sSL https://lambci.s3.amazonaws.com/binaries/gcc-4.8.5.tgz ++ tar -xz -C /tmp ++ set +x GCC setup complete /bin/bash: line 1: 33 Segmentation fault (core dumped) npm install Build #1 failed: Command ". ~/init/gcc && npm install && npm run test" failed with code 139
. ~/init/gccpart, then build will succeed
FROM mhart/alpine-node:6 RUN apk update && \ apk upgrade && \ apk add \ util-linux \ pciutils \ usbutils \ coreutils \ binutils \ findutils \ grep \ curl \ bash \ git RUN apk add \ python \ py-pip \ && \ pip install --upgrade awscli WORKDIR /tmp/lambci/build USER root # Build node_modules ADD package.json /buildserver/ RUN cd /buildserver && npm install # Now add the rest, the above layers will be cached if package.json doesn't change ADD . /tmp/lambci/build # Move npm modules over RUN rm -rf /tmp/lambci/build/server/node_modules && mv /buildserver/node_modules /tmp/lambci/build/server/ RUN cd /tmp/lambci/build && ./lambci.sh
run, but it is not clear to me how to pass a shell script to the run stage. Maybe if I could leverage $LAMBCI_DOCKER_RUN_ARGS?
mhart continues to already-do-things-a-year-ago that i've just now thought about.
i have a slow lambda fn that i'm thinking about moving off of lambda. but i'd like to avoid refactoring bc it's just a test and i think the reason for the move is temporary.
is anyone aware of something that'd let me ship an existing lambda function using ecs? https://github.com/lambci/ecs seems like a good start, but that's purpose-built for lambci. maybe there is something out there for just this purpose?
my goal is to continue building for lambda and as needed, move functions off lambda into ecs or back.