Error while running run_docker_build.sh
See original GitHub issueWhen executing staged-recipes/.circleci/run_docker_build.sh
, I’ve gotten this error multiple times, even after rebasing from the upstream master
Verifying transaction: ...working... done
Executing transaction: ...working... done
+ export FEEDSTOCK_ROOT=/home/conda/staged-recipes
+ FEEDSTOCK_ROOT=/home/conda/staged-recipes
+ export CI_SUPPORT=/home/conda/staged-recipes/.ci_support
+ CI_SUPPORT=/home/conda/staged-recipes/.ci_support
/home/conda/staged-recipes/.circleci/build_steps.sh: line 48: CONFIG: unbound variable
https://github.com/conda-forge/staged-recipes/blob/master/.circleci/build_steps.sh#L48
I’m unsure of how to fix this @conda-forge/staged-recipes
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Npm run build failing when running docker build
I'm getting an error when I run docker build . The problem is when docker runs npm install -f , initially I changed...
Read more >build.sh not found when doing docker build #30 - GitHub
I have the exact same issue . Running Docker Desktop for Windows 2.2. Step 10/14 : RUN build/build.sh ---> Running in 32c9d6d4aff7 /bin/sh...
Read more >Error when running Docker with entrypoint script in Linux VM
I am running several dockers inside the CircleCI Linux VM when configured with machine: true and I am building and then running a...
Read more >[solved] Failing to build dockerfile for ARM servers; rpc error ...
I wrote a dockerfile, put it on github and added the docker.publish action file. It's meant to run a small single server application...
Read more >Using Docker with Pipeline - Jenkins
Many organizations use Docker to unify their build and test environments across machines, and to provide an efficient mechanism for deploying applications.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just ran into this problem as well when trying to test a recipe locally. Could this be documented somewhere? I don’t see any mention of it at https://conda-forge.org/docs/maintainer/adding_pkgs.html#running-tests-locally-for-staged-recipes
In my case I fixed it with:
but it would be nice to know up front that it refers to the YAML files in the same
.circleci
directory.Ahhhh to the conda forge GitHub io repo that holds the main documentation.