![]() ![]() I’m doing something that is deprecated and someone flipped the switch to end support yesterday) or there is an CircleCI issue/bug. prob overkill but makes sure youre not using old containers. To start the services Run: docker-compose build. Since it used to work reliably and still works locally, I’m assuming that the problem is either with my CircleCI config (e.g. Also Before you start your app run these commands to clean up any old containers/networks: docker-compose kill docker-compose down docker network prune docker volume prune. I’ve tried googling for docker error code 239 but have come up empty. I can build the image on my local machine without issue. The command ‘/bin/sh -c npm install -g -s -no-progress yarn & rm -rf node_modules & yarn install & yarn cache clean’ returned a non-zero code: 239 Step 4/12 : RUN npm install -g -s -no-progress yarn & rm -rf node_modules & yarn install & yarn cache clean Removing intermediate container fca7f7d18cee ![]() Status: Downloaded newer image for node:10-alpine The relevant config looks like this: publish:ĭocker build -t $IMAGE_NAME:$TAG -t $IMAGE_NAME:latest. Solution 1: sudo docker build -, my code inside the dockerfile., will increase the build time and the size of the image., the steps to build that same large. This is pretty perplexing as the build configuration hasn’t changed and it worked for weeks up until yesterday. The problem is when docker runs npm install -f, initially I changed the command to npm install but the problem still persists. ![]() Create a Dockerfile in this folder and add the following commands. All of my build steps that build docker images are failing since yesterday. Create a local directory on your development machine that we can use as a working directory to save our Dockerfile and any other files that we’ll need for our development image. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |