After updating my docker image and pushing to ghcr, the changes are not available when running the workflow!

Could you show us exactly how the update and push happens? The way the image is used looks correct (assuming the credentials are), so it’s probably something there.

The Dockerfile is pushed manually to mitigate any issues:

docker build -t image:latest
docker tag hash ghcr.io/org/image:latest
docker push ghcr.io/org/image:latest

The project requires Rust, Rustup, Cargo, etc. Which is all in the Dockerfile, as tested locally.

For some reason, rustup should be located in /github/home/.cargo, instead of the default cargo installation directory which is /root/.cargo/bin.

This step is done in the Dockerfile, as:

ln -s "/root/.cargo/bin" /github/home/.cargo

Which then, when I do open a shell session locally to the Docker instance, I confirm everything is ok and operates as expected:

docker run -v $(pwd):/github/workdir/ -it ghcr.io/org/image:latest /bin/bash

Lists the expected files or symlink when:

ln -ls /github/home

Now, in the cloud, if I do the same as done locally:

jobs:
  build:
    runs-on: ubuntu-latest
    container:
      image: ghcr.io/org/image:latest
      credentials:
        username: ${{ github.actor }}
        password: ${{ secrets.PRIVATE_ACCESS_TOKEN }}
steps:
  - name: DEBUG
    run: |
      ls -la /github/home

The output is empty or does not have the .cargo symlink!

.
..

I understand I can have the Rust Toolchain github action, but if I go with this option, I need to build Rust source code which is extremely slow. I also understand I can use cache by using key names and validation but I just want to use the Docker instance as I have tested locally and not have to include or build certain dependencies.

      - name: Rust toolchain
        uses: actions-rs/toolchain@v1
        with:
          toolchain: stable
          target: wasm32-unknown-unknown

Just thought about something that I need to test.

The path I’ve been using in the Docker file is:

ENV PATH="/root/.cargo/bin:${PATH}"

But I’ll now try:

export PATH="$HOME/.cargo/bin:$PATH"

And also:

ln -s "/root/.cargo/bin" "$HOME/.cargo"

Actually this wouldn’t work as effectively, $HOME throws, when running locally:

failed to create symbolic link '/root/.cargo/bin': File exists

So, I guess the original should be alright:

RUN ln -s "/root/.cargo/bin" /github/home/.cargo

And probably this /github/home location is a volume that is mounted automatically maybe?! And so anything I do in advance is effectively removed?! I do remember testing doing the symlink as a step in the github action workflow, but can double check.

Thanks! That’s good to know, hope it helps other users.

I have also tried the symlink in the Github Action workflow, but I will double check (what I meant is, during some testing, for alternative solutions). If do it as a step in the workflow, do you think it’ll work?

Initialize containers

Do you know when the doc for “Initialize containers” is located? trying to find it

I don’t think there is a specific documentation. I mean you should check the workflow logs, where you can see the exact commands the runner is using. Here’s an example from one of my workflows:

grafik794×726 108 KB

Thank you for letting me know!

What a gem, I didn’t know that either!