My specific situation is that I have a bitbucket pipelines file that uses an AWS-CLI docker image as a service container. My pipeline step script runs `aws` commands to set some configurations before running an AWS S3 sync of files generated on the main container to a specified endpoint in S3. The problem is that I end up with the following error:
bash: aws: command not found
I defined the service definition to use the `xueshanf/awscli` image. Am I simply using the wrong one, or do I need to pass additional Docker run options in the pipeline file? I didn't see any options for that in the documentation.
I'm thinking I misunderstood how Docker works in this context. I was under the assumption that it would expose the `aws` command to the main container. It seems as though it doesn't do that, and I can't use
docker run ...
since that is unsupported.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.