Steps are not executed correctly when being ran in image built in previous job (from Github Packages)

[stex]

Hey!

It’s a bit difficult to find a good title for this issue (which might be the reason I didn’t find any solution for my problem through Google yet…)

I’m building a very simple image in the first job of my workflow:

FROM ruby:3
WORKDIR /app
COPY ./Gemfile ./Gemfile.lock ./

RUN bundle config set --local path '/gems'

RUN bundle install --jobs=$(nproc)
COPY ./ ./
CMD ["/bin/bash"]

This image is pushed to Github packages and I am able to pull it locally and run commands inside the corresponding container as expected, in this case

docker run -it --rm THE_IMAGE:TAG bundle exec standardrb

However, when running the job in Github Actions, I get the following result:

image553×636 37.5 KB

I added a simple ls -la to see where I was. Surprisingly, the workspace inside the action seems to be empty, leading me to the assumption that I’m not inside the correct container at all.

My workflow looks like this:

name: test
on:

push
pull_request

env:

REGISTRY: docker.pkg.github.com

IMAGE_TAG: docker.pkg.github.com/stex/my_repo/the_image_name:${{ github.sha }}
jobs:

build:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v2

- uses: satackey/[email protected]

continue-on-error: true

- run: docker login ${REGISTRY} -u ${GITHUB_ACTOR} -p ${{ github.token }}

- run: docker build -t ${IMAGE_TAG} -f Dockerfile.dev .

- run: docker push $IMAGE_TAG

standardrb:

runs-on: ubuntu-latest

needs: build

container:

image: docker.pkg.github.com/stex/my_repo/the_image_name:${{ github.sha }}

options: "--entrypoint /bin/bash"

credentials:

username: ${{ github.actor }}

password: ${{ github.token }}

steps:

- run: ls -la

- run: bundle exec standardrb

The documentation for running code inside an own container isn’t too extensive, but I’ve used this flow in Gitlab CI for a long time with great results.

Am I missing something really simple here?

Thanks a lot in advance!

[airtower-luna]

Your Dockerfile sets this:

Stex:

WORKDIR /app

So /app is where your data ends up. However, when you use a container image for a job (as in your second job) settings like working directory or entrypoint are ignored. The actions runner mounts the job workspace into the container and uses that as the working directory. The logs for the “Initialize containers” step should show you all the Docker arguments that are used to start the container.

If you want to run the things in /app within the container you’ll need to change the directory, either as part of your step or using the working-directory keyword.

[stex]

Looks like I’ve been too spoiled by Gitlab where everything just works as expected (and every command is ran inside the same container).

- run: cd /app && bundle exec standardrb

solved the problem for me.

airtower-luna:

The logs for the “Initialize containers” step should show you all the Docker arguments that are used to start the container.

You are right, it does. I missed that __w is mounted in the container with workdir being set to a path inside it. In my defense, that’s a 5 line docker create statement 🙈

Thanks a lot for your help, maybe an actual example of how to properly use own, pre-built images in actions would make a good addition to the documentation.