Markus Falb

I did habe troubles with underscores in hostnames before. According to RFC 952 underscores are not valid, and I think that some versions of linux (glibc?) follow that more strictly...

FWIW, I managed to trigger the sudo error without using molecule. It happens when there is no entry in /etc/hosts in the container. I created my test container with `podman...

redirecting is easy, but it has no timestamps. however, may I suggest considering logging to syslog? this would also be helpful for all those who are logging to a central...

It happened to me too yesterday when running molecule test. Sounds similar enough. I was running "molecule test" but had ANSIBLE_COLLECTIONS_PATH=../../.. in my environment which I find sometimes necessary. Not...

There's another solution. Note that podman has a --systemd switch with that a lot of things happens implicitly, you don't need to specify tmpfs no more. ```yaml platforms: - name:...

> @mafalb I also did the same in our project, but my real concern is if we are facing the issue then it needs to be well documented. But I...

> `systemd: true` was supposed to set the command to run, but it was not being picked up for me and I needed to explicitly set it. It depends how...

I think the error message means that no directory named ```molecule/default/molecule.yml``` exists. Sometimes this happens to me when I am running molecule while in the wrong current working directory. Looking...

It's a image running systemd? See https://ansible.readthedocs.io/projects/molecule/guides/systemd-container/ or use ```systemd: always```, that should also work IMO. The reason for the error is IMO that you do not mount /tmp as...

> or use `systemd: always`, that should also work IMO. I realise that you use docker, not podman. Maybe the `systemd: always` shortcut does only exist with podman.