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
If using the legacy distribution provided docker yum packages (1.13.1) there is no working combination of the following parameters due to wrong regexes in
if ($version != undef) and ($version =~ /^(17[.]0[0-4]|1.\d+)/) {
version (specify or leave empty)
root_dir (I need that)
use_upstream_package_source => false (as documented in the README)
service_overrides_template => false (as documented in the README)
docker_ce_package_name => 'docker' (as documented in the README)
Actual Problem
If version is specified, all docker_ce_* parameters are ignored.
If version is not specified, the root_dir_flag will be '--data-root', which does not yet exist in 1.13.1.
Environment
any module version, but used latest 9.1.0
CentOS 7
Some thoughts
The regexes trying to cover 1.x are wrong anyway:
1.\d+
matches ANY character after 1, which is not intended...
And what about versions 0.x?
I would come up with the following for 0.x and 1.x:
[01][.]\d+[.]\d
which also addresses semver conformity.
The text was updated successfully, but these errors were encountered:
If using the legacy distribution provided docker yum packages (1.13.1) there is no working combination of the following parameters due to wrong regexes in
puppetlabs-docker/manifests/init.pp
Line 546 in c861112
and
puppetlabs-docker/manifests/init.pp
Line 609 in c861112
Actual Problem
If version is specified, all docker_ce_* parameters are ignored.
If version is not specified, the root_dir_flag will be '--data-root', which does not yet exist in 1.13.1.
Environment
Some thoughts
The regexes trying to cover 1.x are wrong anyway:
1.\d+
matches ANY character after 1, which is not intended...
And what about versions 0.x?
I would come up with the following for 0.x and 1.x:
[01][.]\d+[.]\d
which also addresses semver conformity.
The text was updated successfully, but these errors were encountered: