podman/pkg/systemd/parser
Mario Loriedo 8e6ecb97c9 Fix running machines with volumes containing spaces
Machines configured to mount local paths containing
spaces failed to start on Hyper-V and silently failed
to mount the folder on macOS/Linux.

On Windows/hyperv, where local paths are mounted
running a 9p client inside the VM, the local host
path needs to be surrounding with quotation marks
before using in a `podman machine ssh ...` command.

A similar behavior happened on Linux/QEMU where the
path was used in a SSH command to mount the folder
using virtiofs. Quoting the path when buidling the
command arguments fixed the problem.

On macOS/libkit,applehv the path was written as is
in a systemd unit name to instruct how to mount it.
Escaping space chars so that they are are parsed
successfully fixed this:
```diff
-- enable path with spaces.mount
++ enable path\x20with\x20spaces.mount
```

Fixes https://github.com/containers/podman/issues/25500

Signed-off-by: Mario Loriedo <mario.loriedo@gmail.com>
2025-04-30 08:54:42 +02:00
..
split.go Fix running machines with volumes containing spaces 2025-04-30 08:54:42 +02:00
split_test.go Fix unescaping octal escape sequence in values of Quadlet unit files 2025-01-14 23:21:47 +01:00
unitfile.go Quadlet - Propagate warnings and print errors and warnings as they occur 2025-03-10 11:51:32 -04:00
unitfile_test.go add support to `;` for comments in unit files as per systemd documentation 2025-01-13 14:20:24 +01:00