Update dependency molecule-docker to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
molecule-docker	==0.2.4 -> ==2.1.0

---

Release Notes

ansible-community/molecule-docker (molecule-docker)

v2.1.0

Compare Source

Minor Changes

• Add support for cgroupns_mode (#​166) @​twouters

Bugfixes

• fix: make sure directory for async is correctly set (#​178) @​gardar
• Fix lint issue (#​170) @​zhan9san
• Sync docker context (#​169) @​zhan9san
• Add support for py310 and py311 (#​160) @​ssbarnea

v2.0.0

Compare Source

Major Changes

• Require molecule 4.0 or newer (#​157) @​ssbarnea
• Require ansible-core 2.12 or newer (#​156) @​ssbarnea
• Drop python 3.6 and 3.7 support (#​141) @​ziegenberg

Bugfixes

• Require community-docker>=3.0.0a2 (#​155) @​ssbarnea
• Add docker_host option in README (#​148) @​zhan9san
• change IRC room from ansible-molecule to ansible-devtools (#​133) @​ziegenberg
• Add platform to the Build an Ansible compatible image task (#​122) @​madrover

v1.1.0

Compare Source

Minor Changes

• Remove setup.py file (#​109) @​ssbarnea
• Require community.docker>=1.9.1 (#​107) @​ssbarnea

Bugfixes

• Fix Deprecation warning for command_handling option (#​100) @​Brettdah
• fix link to community.docker (#​102) @​rndmh3ro
• Ensure we use fully qualified module names (#​104) @​ssbarnea
• Fix delete network task when option (#​97) @​cursedclock

v1.0.2

Compare Source

Minor Changes

• Use cache from ansible-compat (#​94) @​ssbarnea

Kudos goes to: @​ssbarnea

v1.0.1

Compare Source

Major Changes

• Default branch is now main and old master was renamed to legacy/master as it included few breaking changes that we did not want
• Rely on community.docker collection (#​58) @​ssbarnea
• Require molecule 3.4.0 or newer (#​84) @​ssbarnea
• Expose required collection (#​77) @​ssbarnea

Minor Changes

• add support for non managed docker networks (#​70) @​hassenius

Bugfixes

• Pass stop_signal and kill_signal to docker_container in create.yml (#​49) (#​60) @​ssbarnea
• Add extra static test (#​59) @​ssbarnea
• Pass stop_signal and kill_signal to docker_container in create.yml (#​49) @​ericcitaire
• Add links parameter to create.yml (#​36) @​ragingpastry
• fix: specify docker modules namespace (#​56) @​Yajo
• Cleanup output, use loop over with_items. (#​33) @​robertdebock
• Pass mounts to docker_container in create.yml (#​46) @​jsparger
• Avoid requiring pre-release version of molecule (#​32) @​ssbarnea
• Fix references to 'env' option (#​27) @​stoned
• change freenode to libera (#​72) @​hassenius
• remove state statement (#​71) @​hassenius
• Enable ansible-lint (#​73) @​ssbarnea
• Fixed package location (#​92) @​ssbarnea

v1.0.0

Compare Source

v0.3.4: yanked

Compare Source

This release was yanked due to major regressions introduced, documented on #​57

Changes

Minor Changes

• change docker image build path (#​51) @​alxgomz
• Pass stop_signal and kill_signal to docker_container in create.yml (#​49) @​ericcitaire
• Add links parameter to create.yml (#​36) @​ragingpastry

Bugfixes

• fix: specify docker modules namespace (#​56) @​Yajo
• Address deprecation warning (#​54) @​ssbarnea
• Fix condition when path is missing (#​55) @​ssbarnea
• Cleanup output, use loop over with_items. (#​33) @​robertdebock
• Pass mounts to docker_container in create.yml (#​46) @​jsparger
• Fix unnecessary warnings when creating/destroying docker networks (#​48) @​mtpettyp
• Avoid requiring pre-release version of molecule (#​32) @​ssbarnea
• Fix references to 'env' option (#​27) @​stoned

v0.3.3: (yanked)

Compare Source

Changes

Major Changes

• Make tests compatible with molecule 3.2 (#​19) @​ssbarnea

Minor Changes

• Enable py39 support (#​21) @​ssbarnea

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Pipfile.lock

Command failed: docker pull docker.io/containerbase/sidecar
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Pipfile.lock

Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot 
install -r /tmp/pipenv-t9vvxuq6-requirements/pipenv-znq82uqs-constraints.txt 
(line 2), -r /tmp/pipenv-t9vvxuq6-requirements/pipenv-znq82uqs-constraints.txt 
(line 6) and molecule==3.4.0 because these package versions have conflicting 
dependencies.
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/resolver.py", line 451, in main
[ResolutionFailure]:       _main(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/resolver.py", line 436, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/resolver.py", line 400, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 1083, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = 
actually_resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 811, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.25/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 471, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=e)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: ResolutionImpossible: for help visit 
https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-depende
ncy-conflicts

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!