actions-runner-controller/runner/supervisor/dockerd.conf

[program:dockerd]
command=/usr/bin/dockerd
autostart=true
autorestart=true
stderr_logfile=/var/log/dockerd.err.log
stdout_logfile=/var/log/dockerd.out.log
Configurable "runner and DinD in a single container" (#126) 2020-10-20 02:48:28 +03:00			`[program:dockerd]`
feat: Add container to propagate host network MTU (#1201) * feat: Add container to propagate host network MTU Some network environments use non-standard MTU values. In these situations, the `DockerMTU` setting might be used to specify the MTU setting for the `bridge` network created by Docker. However, when the Github Actions workflow creates networks, it doesn't propagate the `bridge` network MTU which can lead to `connection reset by peer` messages. To overcome this, I've created a new docker image called `summerwind/actions-runner-mtu` that shims the docker binary in order to propagate the MTU setting to networks created by Github workflows. This is a follow-up on the discussion in (#1046)[https://github.com/actions-runner-controller/actions-runner-controller/issues/1046] and uses a separate image since there might be some unintended side-effects with this approach. * fixup! feat: Add container to propagate host network MTU Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com> 2022-09-23 09:08:28 +01:00			`command=/usr/bin/dockerd`
Configurable "runner and DinD in a single container" (#126) 2020-10-20 02:48:28 +03:00			`autostart=true`
			`autorestart=true`
			`stderr_logfile=/var/log/dockerd.err.log`
			`stdout_logfile=/var/log/dockerd.out.log`