actions / actions/actions-runner-controller
Not able to silent INFO logs in dind Ubuntu 20.04 image
Open
Nobody has claimed this yet.
bug
community
needs triage
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Checks
- I've already read https://github.com/actions/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.
- I'm not using a custom entrypoint in my runner image
Controller Version
0.27.3
Helm Chart Version
No response
CertManager Version
No response
Deployment Method
Other
cert-manager installation
Cert Manager is installed and working as expected.
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
- I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
- My actions-runner-controller version (v0.x.y) does support the feature
- I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
- I've migrated to the workflow job webhook event (if you using webhook driven scaling)
Resource Definitions
NA
To Reproduce
Run the dind ubuntu 20.04 image
Describe the bug
Info logs are visible for daemon
Describe the expected behavior
Docker info logs should not be coming once We set the log-level to error in /etc/docker/daemon.json
Whole Controller Logs
NA
Whole Runner Pod Logs
2023-11-09 08:43:00.976 NOTICE --- Runner init started with pid 9
Using /etc/docker/daemon.json with the following content:
---
{
"log-level": "error"
}
---
2023-11-09 08:43:00.979 DEBUG --- Starting Docker daemon
2023-11-09 08:43:00.981 DEBUG --- Waiting for processes to be running...
2023-11-09 08:43:01.12 DEBUG --- dockerd is running
* Restarting periodic command scheduler cron
* Stopping periodic command scheduler cron
...done.
* Starting periodic command scheduler cron
...done.
2023-11-09 08:43:01.27 DEBUG --- Github endpoint URL https://github.com/
root is not in the sudoers file. This incident will be reported.
time="2023-11-09T08:43:01Z" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"
time="2023-11-09T08:43:01.080507655Z" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
2023-11-09 08:43:02.429 DEBUG --- Configuring the runner.
--------------------------------------------------------------------------------
| ____ _ _ _ _ _ _ _ _ |
| / ___(_) |_| | | |_ _| |__ / \ ___| |_(_) ___ _ __ ___ |
| | | _| | __| |_| | | | | '_ \ / _ \ / __| __| |/ _ \| '_ \/ __| |
| | |_| | | |_| _ | |_| | |_) | / ___ \ (__| |_| | (_) | | | \__ \ |
| \____|_|\__|_| |_|\__,_|_.__/ /_/ \_\___|\__|_|\___/|_| |_|___/ |
| |
| Self-hosted runner registration |
| |
--------------------------------------------------------------------------------
# Authentication
√ Connected to GitHub
# Runner Registration
√ Runner successfully added
√ Runner connection is good
# Runner settings
√ Settings Saved.
2023-11-09 08:43:09.373 DEBUG --- Runner successfully configured.
2023-11-09 08:43:09.375 DEBUG --- Docker enabled runner detected and Docker daemon wait is enabled
2023-11-09 08:43:09.376 DEBUG --- Waiting until Docker is available or the timeout of 120 seconds is reached
}CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2023-11-09 08:43:09.397 NOTICE --- WARNING LATEST TAG HAS BEEN DEPRECATED. SEE GITHUB ISSUE FOR DETAILS:
2023-11-09 08:43:09.398 NOTICE --- https://github.com/actions/actions-runner-controller/issues/2056
√ Connected to GitHub
Current runner version: '2.311.0'
2023-11-09 08:43:12Z: Listening for Jobs
2023-11-09 09:53:26Z: Running job: Build Checkout Native (linux-amd64)
time="2023-11-09T09:53:50.726577097Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-11-09T09:53:50.726639187Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-11-09T09:53:50.726650938Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-11-09T09:53:50.726896132Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/c69c66da4be77c4945bc5f9e2df46a0b81562b832c930e99df6918a6bd90a08c pid=820 runtime=io.containerd.runc.v2
time="2023-11-09T10:00:25.982463553Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-11-09T10:00:25.982525791Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-11-09T10:00:25.982536533Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-11-09T10:00:25.982827540Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/03150499538cd4b52ed522f8c840f1ed8d3d49c17e3c25b8041b49500192d09b pid=2162 runtime=io.containerd.runc.v2
time="2023-11-09T10:00:31.179111174Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-11-09T10:00:31.179174230Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-11-09T10:00:31.179191093Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-11-09T10:00:31.179697895Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/09e76e1aaaccf43481c4e2665a4642a9d707deaaa7ebdabc44b08adac6f23935 pid=2387 runtime=io.containerd.runc.v2
time="2023-11-09T10:01:00.397332563Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-11-09T10:01:00.397413471Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-11-09T10:01:00.397429958Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-11-09T10:01:00.397644030Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/2713b41e7a472d62ae6dce714c0ead5d5c393d5948249cf2c35f46e2a8923ac6 pid=2597 runtime=io.containerd.runc.v2
time="2023-11-09T10:01:12.345069599Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-11-09T10:01:12.345170184Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-11-09T10:01:12.345187492Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-11-09T10:01:12.345400551Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/4d904f3c2d63b3856933ab57c13231b991438f8acfa9a5288f31b25a367e8c4b pid=3049 runtime=io.containerd.runc.v2
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the dind Ubuntu 20.04 image and inspect how /etc/docker/daemon.json is applied to Docker and its containerd processes. Verify which process emits the INFO lines and confirm that setting the log level to error suppresses the reported messages without breaking runner jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ubuntu
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100