Jared Hampson

I tried running v6.0 on a GitHub-hosted runner and it ran successfully. Looking at `actions/http-client` that has `tunnel` dependency, it looks like it is only referenced when the runner is...

Since this was originally opened, the docker-ipv6nat repo mentioned above has pinned an [issue considering deprecation](https://github.com/robbertkl/docker-ipv6nat/issues/65) due to recent progress in Docker for built in IPv6 NAT support.

Usually we have it configured as group_vars in inventory, such as ``` # group_vars/windows.yml ansible_connection: winrm ansible_winrm_transport: kerberos ``` It seems like we should be able to do the same...

Create a file at `/etc/systemd/resolve.conf.d/resolve.conf` and with the contents: ``` [Resolve] DNS=192.168.178.1 DNSStubListener=no ``` Or whatever set of options is appropriate for your system. And `systemctl restart systemd-resolved` This file...

It looks like the Pester5 result object has changed significantly since v4 and no longer has a `failedcount` property. Helper command `ConvertTo-Pester4Result` is available to transform a v5 result object...