Miika Kankare

I think I'm seeing the same issue. `image_strict` didn't seem to help.

``` - name: Create a container become: true become_user: grafana containers.podman.podman_container: name: grafana image: docker.io/grafana/grafana image_strict: true state: present register: podman_container - name: Create a container become: true become_user: grafana...

I intend to run these without root, but tested that as well just to see if it works differently. Same result.

Apparently the systemd unit file content is not being created if `no_header` is set to `true`. Probably not related to this, but something funky is going on. :)

@sshnaidm Yeah, I've been trying with the above example without `generate_systemd`. But, this is probably working as expected! Or the ID of the image is indeed the same if that...

Yup, Debian stable being very stable. :) I have a fairly good workaround for this in place, so I'm okay leaving it as is. If the warning is not too...

I'm not quite sure if I'm hitting this same issue or not, but I've been trying to add [Requarks/wiki](https://github.com/Requarks/wiki/tree/dev/dev/helm) to no avail with `helm-git` either directly or through `helmfile`. ```...

I worked around this with the [user_data](https://github.com/test-kitchen/kitchen-openstack#user_data) support of the driver. It's a bit ugly, but works. Obviously, I'd rather have support for synced folders as well. :)

Encountered the same thing with the `route53` module. Works without `strategy: mitogen_linear` as well.

Currently using `tfcmt` which does create a new comment for each workflow, but was thinking of changing to `tfnotify` (for other reasons). In any case, I would like to have...