Container volumes key not mounting volume

When running containers within a job, using the volumes key doesn’t appear to mount any matching volumes on the container (not visible in the call to docker create call).

Using the options key with the exact same path with ‘-v’ flag works as expected. Is anyone else experiencing this?


I’m experiencing the same problem:

        - /hsmtmp:/tmp

in the container inicialization there is no mention to the volume requested:

/usr/bin/docker create --name ea6805f1d30f42d79eed7117eb9535f5_enilton_rev005_17c4f0 --label 10865d --workdir / w/hsm_firmware/hsm_firmware --network github_network_18903fabce10451ebab4c20d6b555d5c --privileged -e “HOME=/github/home” -e GITHUB_ACTIONS=true -v “/var/run/docker.sock”:"/var/run/docker.sock" -v “/home/runner/work”:"/ w" -v “/home/runner/runners/2.160.0/externals”:"/ _e":ro -v "/home/runner/work/temp":"/ w/_temp" -v “/home/runner/work/_actions”:"/ _w/actions" -v “/opt/hostedtoolcache”:"/ t" -v “/home/runner/work/_temp/_github_home”:"/github/home" -v “/home/runner/work/_temp/_github_workflow”:"/github/workflow" --entrypoint “tail” enilton/rev0:0.5 “-f” “/dev/null”

I also don’t see any information related to volumes printed in the “Initialize containers” step. Cannot see mounted directories on host or within the container also.

I am facing the same issue, does someone know if this is known by github?

I experienced this today too, used the “options: -v <volume>” workaround suggested above. 

1 Like