WIP: Update default molecule scenario + fix verify #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using geerlingguy/docker-debian10-ansible + geerlingguy/docker-debian11-ansible in Ansible molecule currently do not work with systemd, see: geerlingguy/docker-debian11-ansible#4. Instead, took Dockfiles from @aussielunix (Thx!) found here (but removed 'Australia/Sydney' timezone): * https://gitlab.com/aussielunix/ansible/molecule-containers/-/blob/main/debian/buster/Dockerfile * https://gitlab.com/aussielunix/ansible/molecule-containers/-/blob/main/debian/bullseye/Dockerfile Compare with @geerlingguy's current Dockerfiles: * https://github.com/geerlingguy/docker-debian10-ansible/blob/6f6a1650421afc953eb11439db9e5dabcc4d3afe/Dockerfile * https://github.com/geerlingguy/docker-debian11-ansible/blob/101602c7b9e7b3e100b7435eaa455b94189b2d47/Dockerfile Note, that when using `dockerfile`, `image` seems to be needed too. Used `docker.io/debian:$DISTRIBUTION-slim` for `image` as they are the base images for @aussielunix's Dockerfiles. I could have used @aussielinux gitlab container registry as `image`, but currently 'debian:bullseye' is missing: * https://gitlab.com/aussielunix/ansible/molecule-containers/container_registry/3343441 See: geerlingguy/docker-debian11-ansible#4 (comment)
To make `molecule verify` work, after we managed to get systemd working in the docker container, we noticed that we had to update the example chrony configuration files. 'gather_facts: true' has to be set, else 'ansible_distribution_release' was undefined.
|
A solution has been proposed, see: geerlingguy/docker-debian11-ansible#4 (comment) + ansible/molecule#3665 (comment):
|
jkirk
added a commit
that referenced
this pull request
Jun 23, 2023
systemd services used to fail (also in the Github Actions). This seems to fix it as proposed in ansible/molecule#3665 (comment) This replaces PR #12.
jkirk
added a commit
that referenced
this pull request
Jun 23, 2023
systemd services used to fail (also in the Github Actions). This seems to fix it as proposed in ansible/molecule#3665 (comment) This replaces PR #12.
jkirk
added a commit
that referenced
this pull request
Jun 23, 2023
systemd services used to fail (also in the Github Actions). This seems to fix it as proposed in ansible/molecule#3665 (comment) This replaces PR #12.
jkirk
added a commit
that referenced
this pull request
Jun 23, 2023
systemd services used to fail (also in the Github Actions). This seems to fix it as proposed in ansible/molecule#3665 (comment) This replaces PR #12.
|
Decided to implement |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
molecule testworks locally, but fails for Debian/bullseye in the Github Action:Also see: geerlingguy/docker-debian11-ansible#4