Josh Babault

Ubuntu Jammy does not have an updated ansible-core version that fixed this bug. You're either using outdate ansible-core or aren't installing the base modules collections.

From what I can remember that seems to be the case; this is all I have from my notes around that time: There was an issue for this: https://github.com/ansible/ansible/issues/76530 It...

Apt is going through pretty big changes as of recent (>2.7.X) if I remember correctly. Make sure you're reading a correctly versioned manpage if you're searching online. Anywho, you can...

Please note the above was done with Podman v4.9.3 which uses different default rootless networking than Podman 5/5.3+. The goal going forward will be to use Podman 5.4.0 as the...

@mathzol In general mail servers should not be run without bastions and other firewalling machines in front of them. Mail servers are a special category of security surfaces that need...

@Hobby-Student https://docs.mailcow.email/getstarted/install/#installing-mailcow `generate_config.sh` creates the `mailcow.conf` file, everything is still run using a compose file

> due to what appears to be a later module load This is probably the issue, the user is likely using a sata/ide based CD-ROM which many guides/tutorials/hypervisor defaults will...

More contextual logs: ``` [2025-10-16 20:28:19.550841] ublk.c: 294:ublk_ctrl_cmd_error: *ERROR*: ctrlr cmd UBLK_CMD_START_DEV failed, Invalid argument [longhorn-instance-manager] time="2025-10-16T20:28:19Z" level=error msg="Failed to create engine pvc-579e0eae-e3bc-464f-88d5-5909dd635c83-e-0" func="spdk.(*Engine).Create.func2" file="engine.go:232" engineName=pvc-579e0eae-e3bc-464f-88d5-5909dd635c83-e-0 error="failed to start initiator...

Upstream Issue: https://github.com/spdk/spdk/issues/3758