Step commands with a custom primary image


#1

Could somebody explain how are step commands actually run in the primary image (the one in jobs.build.docker[0].image)? There’s no explanation to that in the docs. I have a custom image my/base which contains my toolchain. On my local box I can do docker run my/base npm --version which works as expected. My Circle step command has npm install in it and it fails with /bin/bash: line 1: npm: command not found.
If I try to and connect to the container, npm works as expected.

More specifically, does CircleCI respect the primary image entrypoint?

Any tips on what may I be doing wrong?


#2

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.