-
Notifications
You must be signed in to change notification settings - Fork 320
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
Update Docker dind to 20.10.7-dind #327
Conversation
There is a problem with the official Docker-in-Docker images that prevents upgrading at the moment. See #306 (comment) |
Either Docker version must be upgraded or #322 must be merged again (can't see why it would cause mentioned issues, possibly these were stray issues unrelated to changes made or possibly users are using cgroupsv2) or we will block using Alpine 3.14 images forever. In addition, the old version of Docker prevents usage of cgroupsv2. |
@CirnoT I've built and pushed my fork here with the linked PR: https://hub.docker.com/r/techknowlogick/drone-docker for arm64&amd64 in case you need it. |
Is it worth holding back for one platform? THis is CI we're talking about here, I'd imagine most CI runs are on amd64 and presumably on Linux anyway. Without the update a lot of folks's workflows that depend on Make and use Alpine are broken. |
So I worked out how to build and use this in my environment, but there are problems with it. See attached log. |
ARM (more specifically however ARM64) is gaining more traction every day, abandoning it here would bring more bad than the Alpine 3.14 issue. |
Regardless of the support of other arches (I agree they should continue to be supproted), I can't even get the Docker daemon started when upgrading the plugin to use |
Ahhh I found what I needed |
@prologic a note, if you use the autoscaler the env var you'll need to set for the autoscaler itself is |
I got this working successfully. So this PR at least is functional. One thing to note for anyone running Drone and Drone Runner(s) in Docker Swarm is to ensure your runners have access to the default
|
@bradrydzewski Debian 11 has been released along with new systemd and unified cgroupsv2. Docker 19 does not support cgroupsv2 and DID will always fail on such setup. Workaround of Is this repository still being maintained or are we to assume that Drone has no intent to move forward with technology and replacement should be found? |
@@ -1,4 +1,4 @@ | |||
FROM arm32v6/docker:19.03.8-dind | |||
FROM arm32v6/docker:20.10.7-dind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverting back to 19.03.8 for arm32 should allow us to move forward with 20.10 on rest of platforms while keeping (on life support, as it seems Docker very much does not care about that platform anymore) arm32 usable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, rolling this back seems pragmatic...
FROM arm32v6/docker:20.10.7-dind | |
FROM arm32v6/docker:19.03.8-dind |
for |
Bump +1 My team is currently stuck manually building our prod images locally due to this CI issue :( Manually setting privileged on the build works with techknowlogik's fork, but doesn't seem like the best route going forward |
This is an alternative to drone-plugins#327. As the discussion on that PR shows, it seems docker is not going to provide updates for the arm32 platform anymore. Fixes drone-plugins#326 and fixes drone-plugins#330.
Also waiting on this. Builds using arm64 are currently broken with this plugin, giving |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we move forward with this?
@@ -1,4 +1,4 @@ | |||
FROM docker:19.03.8-dind | |||
FROM docker:20.10.7-dind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
20.10.9 is available now...
FROM docker:20.10.7-dind | |
FROM docker:20.10.9-dind |
@@ -1,4 +1,4 @@ | |||
FROM arm32v6/docker:19.03.8-dind | |||
FROM arm32v6/docker:20.10.7-dind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, rolling this back seems pragmatic...
FROM arm32v6/docker:20.10.7-dind | |
FROM arm32v6/docker:19.03.8-dind |
@@ -1,4 +1,4 @@ | |||
FROM arm64v8/docker:19.03.8-dind | |||
FROM arm64v8/docker:20.10.7-dind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
20.10.9 is available now...
FROM arm64v8/docker:20.10.7-dind | |
FROM arm64v8/docker:20.10.9-dind |
This is an alternative to drone-plugins#327. As the discussion on that PR shows, it seems docker is not going to provide updates for the arm32 platform anymore. Fixes drone-plugins#326 and fixes drone-plugins#330.
Does anyone have a working docker image of drone plugins that works for newer docker versions? This is stopping my arm deploys for weeks now. |
Closing as no longer required. |
Fixes #326
I believe this resolves the issue I described in #326
I'm not sure how to test this myself, without just building my own plugins/docker
which I haven't done bfore...