Apologies if this question has been answered before, I combed the forums and couldn’t see anything specific to my issue, nor did my Google-Fu return anything useful.
Pre-apologies if this does not fit this sub.
What I am trying to do:
- I am using hosted Octopus Deploy. I need to run an AWS CloudFormation job from a Octopus worker. The job is written in NodeJS.
How I am trying to do it:
- I am trying to use a dynamic Ubuntu 18.04 worker node that is offered on the hosted Octopus Deploy variant.
- I am trying to get the Ubuntu worker node to spin up a custom Alpine container from AWS ECR that contains all dependencies for the deployment. (I don’t want to have to install all dependencies on the worker directly per deployment).
- I am trying to run a script in a GitHub repository on the Alpine container.
What is happening:
- The Ubuntu worker node gets the Alpine container and the GitHub repository containing the script successfully.
- The GitHub repository is unzipped to
50at the end). This is the current working directory for this step.
- The Ubuntu worker then spins up the Alpine container successfully, but mounts the wrong directory. It mounts
/home/Octopus/work/xxxxxxxxx-xxxx-51(notice the working directory has changed
- The script attempts to execute an fails with
standard_init_linux.go:211: exec user process caused "no such file or directory"which appears to be a Docker error message. A verbose message states that
Process /bin/bash in /home/Octopus/work/xxxxxxxxx-xxxx-51exited with code 1 `
What I have already tried:
- Running the same steps above but directory on the Ubuntu worker. It is successful as the working directory is not changing from
- Moving the package to
/home/Octopus(as this directory is mounted within the Alpine container), then using an inline script (i.e. copy/pasted code directly into the step rather than an external script from GitHub) to call the script that was moved to
/home/Octopus. This fails as the inline script in the step is being placed into working directory
51is being mounted to the container.
- Simply running an inline script within a container. Also fails with the same issue of the wrong working directory.
Any help to be able to even run a
Hello World script from within my Alpine container will be greatly appreciated!!!