Closed martinm82 closed 2 years ago
Ah right, in the tests I'm pinning it with the 5:
part included https://github.com/nickjj/ansible-docker/blob/master/tests/test.yml#L7.
I feel like I avoided using *[version]*
as the pin because it didn't pick it up as a match but maybe that needs to be revisited.
You are right, I should have checked the tests before opening this ticket. So shall we just update the docs and state to use the version used by apt itself?
I recall 5:
being around for a while but I'm not sure if it'll be consistent for every release of Docker. It feels like it should be both a documentation fix as well as modifying the default main.yml file to also use it so the role works out of the box.
Hi, I put up a PR at https://github.com/nickjj/ansible-docker/pull/113 which pins things using Pin: version *{{ docker__version }}*
which should allow you to set docker__version: 19.03
instead of 5:19.03
and still have the pin work.
Would you mind testing that PR?
This has been fixed in https://github.com/nickjj/ansible-docker/commit/a9b15c9ddd43ed61ab8e0ca97fdbc1092af2b0e1 and is available in v2.2.0 of this role.
When specifying the
docker__version
to19.03
the role is still installing the latest and greatest (as of today 20.10) on the target host.I believe that the problem is the apt pinning config file. When using as version
5:19.03
the latest version of19.03
is installed. This version string is based on the output ofapt-cache madison docker-ce
.