Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runner image Error/Bug: OCI runtime exec failed: exec failed #190

Closed
erikkn opened this issue Nov 15, 2020 · 4 comments
Closed

Runner image Error/Bug: OCI runtime exec failed: exec failed #190

erikkn opened this issue Nov 15, 2020 · 4 comments

Comments

@erikkn
Copy link
Contributor

erikkn commented Nov 15, 2020

Hey, guys!

I was hoping the community could help me out with the following issue I am facing. I have been troubleshooting this error quite a lot with custom images etc. but I amrunning out of ideas. Please note that I am having this issue with the default (summerwind/actions-runner) image as well with custom images.

General information:

Running on: AWS EKS (managed-node-groups)
EKS version: v1.18.8-eks
Controller deployment template image: summerwind/actions-runner-controller:v0.11.3

My runner.yaml

apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: gha-runner
spec:
  replicas: 2
  template:
    spec:
      labels:
        - eks-runner
      organization: "<org name>"
      dockerdWithinRunnerContainer: false
      image: <check below>

Due to this (#174) issue, I decided to use the Dockerfile specified in that same issue (#174 (comment)):

FROM summerwind/actions-runner

# Fix the permission issue on the docker containers
COPY permissions.sh /runner

CMD /runner/permissions.sh && /runner/entrypoint.sh

Reproduce steps

When I deploy my runner.yaml the RunnerDeployments looks fine. When I exec into my runner container and docker container, I am able to run the Docker commands e.g. docker ps, docker run ubuntu:latest).
I double-checked Docker by using a very simple custom workflow that pulls, build, runs 'echo hello world', and pushes a Docker image and that all works fine.

However, when I run this workflow, I am getting the error as shown at the bottom.

name: Build, Test & Upload Service

on:
  pull_request:
  push:
    branches:
      - master
jobs:
  build_service:
    name: Build 
    runs-on: [self-hosted]
    container: <custom image>

    steps:
      - uses: actions/checkout@v2
      - name: Checkstyle Main
        run: ./gradlew checkstyleMain --info
      - name: Checkstyle Test
        run: ./gradlew checkstyleTest --info
      - name: Checkstyle Integration Test
        run: ./gradlew checkstyleIntegrationTest --info

Expected behavior

Job runs fine.

Actual behavior / Error

/usr/local/bin/docker exec  0712ca6bb1f7951bd47b4e43a7c86611e41ea24042a80e4c01192869a6d50322 sh -c "cat /etc/*release | grep ^ID"
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/__e/node12/bin/node\": stat /__e/node12/bin/node: no such file or directory": unknown

When running the workflow/job I receive the error shown above. Installing nodejs in the runner image doesn't fix this issue.
Using this (actions/checkout#334 (comment)) suggestion, by making some manual changes to the runner and running (kubectl exec) /__e/node12/bin/node --version the output looks fine. Unfortunately, after running the workflow I receiveive the same error.

@erikkn
Copy link
Contributor Author

erikkn commented Nov 15, 2020

@mumoshu I am sorry for tagging you all over the place 😅 , but since I am having this issue with the default image as well, I thought it might be better to open a new issue so that other people can track it as well.

@erikkn
Copy link
Contributor Author

erikkn commented Nov 15, 2020

It looks like things work fine using v1 of the checkout package, but the latest version (at this time) is 2.3.4

Working:

    steps:
      - uses: actions/checkout@v1

Obviously v1 is not great, anyone has an idea :)?

@erikkn erikkn closed this as completed Nov 15, 2020
@erikkn erikkn reopened this Nov 15, 2020
@erikkn
Copy link
Contributor Author

erikkn commented Nov 16, 2020

I am running into the same issue with the actions/cache@v1 AND actions/cache@v2 step:

Run actions/cache@v1 (same error with v2)
/usr/bin/docker exec  3fc9226c9720c52dfb0e97d54ec22d71f07594a88b1d015f74a54c78ab882bf4 sh -c "cat /etc/*release | grep ^ID"
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/__e/node12/bin/node\": stat /__e/node12/bin/node: no such file or directory": unknown

@erikkn
Copy link
Contributor Author

erikkn commented Nov 25, 2020

Fix for this issue: #203

@erikkn erikkn closed this as completed Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant