Files installed via curl in build command not persisting to runtime environment

1

I’m trying to install a CLI tool during the build phase and use it during runtime in my web service.

The issue:

  • The build command succeeds (installs the cli tool successfully)
  • Python packages installed via pip persist to runtime
  • But the cli tool (installed via curl) doesn’t persist to runtime
  • When SSHing into the runtime environment, the bins doon’t exist

If I SSH into the runtime environment and run the same curl install command manually, it works fine. This suggests something about the build-time installation isn’t persisting to runtime.

Question: How can I ensure files installed during the build phase persist to the runtime environment? Is there a recommended pattern for installing CLI tools that need to be available during runtime?

2

Anything done during the build step is saved into the deployment artifact, used on every boot. I can’t explain files not existing, but being unable to be run might be a permission issue, e.g. the CLI tool not getting chmod’ed to 755. Can you provide output demonstrating these issues? Showing them in the build and deployed-running states?