-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open
Labels
enhancementNew feature or requestNew feature or requestfutureFeature work that we haven't prioritizedFeature work that we haven't prioritized
Description
I use Bottlerocket AMI on EKS clusters which use containerd that does not uses docker or docker socket.
Custom actions fails with errors like these. As a workaround, is there a way I can use a pre-pulled docker image instead of GitHub action trying to build an image on the fly?
Build container for action use: '/runner/_work/_actions/aevea/commitsar/v0.16.0/Dockerfile'.
/usr/local/bin/docker build -t 60e226:7de2787af7e04b038ce49eb6a1a987d8 -f "/runner/_work/_actions/aevea/commitsar/v0.16.0/Dockerfile" "/runner/_work/_actions/aevea/commitsar/v0.16.0"
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Warning: Docker build failed with exit code 1, back off 8.072 seconds before retry.
/usr/local/bin/docker build -t 60e226:7de2787af7e04b038ce49eb6a1a987d8 -f "/runner/_work/_actions/aevea/commitsar/v0.16.0/Dockerfile" "/runner/_work/_actions/aevea/commitsar/v0.16.0"
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Warning: Docker build failed with exit code 1, back off 4.07 seconds before retry.
/usr/local/bin/docker build -t 60e226:7de2787af7e04b038ce49eb6a1a987d8 -f "/runner/_work/_actions/aevea/commitsar/v0.16.0/Dockerfile" "/runner/_work/_actions/aevea/commitsar/v0.16.0"
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: Docker build failed with exit code 1
sammcj, oleksandr-ivanov-ah, strantalis, myoung34, RomanNess and 40 more
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestfutureFeature work that we haven't prioritizedFeature work that we haven't prioritized