adoptium
Request for update docker to 20.10.11 on machines labeled `dockerBuild&&linux&&x64`
Details:
Docker version on current machines labeled dockerBuild&&linux&&x64 (including dynamic docker machines from Azure)
is Docker version 20.10.7, build 20.10.7-0ubuntu5~20.04.1
Installer jenkins job use dockerBuild&&linux&&x64 to generate rpm packages, which requires docker 20.10.11 when update the fedora to 35.
Could we update docker to 20.10.11 on those machines without affect other jobs assigned to them? Or should we reassign specified machine with docker 20.10.11 to installer jenkins job?
What is it specifically that requires the new version of docker? Can you let us know the failure so we can assess priority and the best course of action? Upgrading docker can be a bit more problematic than some other tooling as it's tied into the kernel a bit more closely, so I'm a little more hesitant to just go for the upgrade without that information.
Is it something that only happens when trying to instantiate a Fedora 35 system and was not a problem with the earlier Fedora? We've got an issue to do some other work with Fedora 35 in containers so would be good to undersdtand if we're likely to hit the same problem with that, or whether it's specific to the installer work.
The Azure dynamic machines are controlled by Microsoft so I have no information on how they are set up - @gdams will have to take that one.
The failure is
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start]
which only happened to 35 as far as I can see. The more details are in https://github.com/adoptium/installer/issues/397
I've restarted the docker service on docker-packet-ubuntu2004-intel-1 which appears to have resolved the problem on that system (Running dnf update in a fedora:35 container now works). As I understand it the docker-packet-ubuntu2004-amd-1 machine was already working properly.
As per previous comment I do not know how to effect a fix on the Azure systems if they are showing the same problem.
Yes, it's still a problem which blocks installer job update to fedora:35 or up.
Since we haven't heard from @gdams on this one perhaps we should see if we can exclude the azure machines from this job for now. The other two that are available have the dockerHost label too - could we add that for the x64 runs?
FYI @steelhead31 sine you're looking at F36 support.
Marking as critical so we can ensure that we determine that there is still something to fix here since there haven't been any comments for a while.
Since there are a number of machines, requiring O/S security updates ( visible in Nagios! ), I'll check and update docker versions on these ( where required ) as part of the patching process. Currently planning this for Friday 14th April 13:00 BST Onwards.
@sophia-guo
There are 2 dockerBuild / linux / x64 machines , that both have versions of docker later than 20.10.11
dockerhost-equinix-ubuntu2004-x64-1 - Docker version 20.10.23, build 7155243
dockerhost-equinix-ubuntu2204-x64-1 - Docker version 20.10.22, build 3a2c30b
Can you confirm that this is ok, if so I can close this issue.