You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current design requires init container, runner and dind (in case of dind).
For dind use-case, can we only use a custom runner+dind, to have a single image? This would be much better for resource efficiency, and setting limits for a single container.
It would also mitigate transient failures like these when the node has some load
Checking docker version
/usr/bin/docker version --format '{{.Server.APIVersion}}'
Cannot connect to the Docker daemon at unix:///run/docker/docker.sock. Is the docker daemon running?
'
Error: Exit code 1 returned from process: file name '/usr/bin/docker', arguments 'version --format '{{.Server.APIVersion}}''.
Did anyone uses a single image for runners (dind scoped)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The current design requires init container, runner and dind (in case of dind).
For dind use-case, can we only use a custom runner+dind, to have a single image? This would be much better for resource efficiency, and setting limits for a single container.
It would also mitigate transient failures like these when the node has some load
Did anyone uses a single image for runners (dind scoped)?
Beta Was this translation helpful? Give feedback.
All reactions