Podman on windows looks in too many (wrong) places for configuration files

[Tyler-IN]

Issue Description

Using ProcMon one can easily monitor process read attempts.

Some paths are not appropriately joined for the roaming app data or program data resulting in missing \ in the 5.1.0-rc1, I will try the release build too.

Probably don't search in C:\usr\share\containers and C:\etc\containers on Windows builds

I think <home>\.config\containers should be fine.

Steps to reproduce the issue

Steps to reproduce the issue

1. Launch ProcMan and configure filters to capture file activity with 'process name is podman.exe' and 'path ends with .conf' as filters.
2. Execute podman.exe
3. Observe captured results in ProcMon.

Describe the results you received

The files being hunted are containers.conf and storage.conf...

• C:\etc\containers\
• C:\usr\share\containers\
• C:\ProgramDatacontainers\
• C:\Users\<Username>\AppData\Roamingcontainers\
• C:\Users\<Username>\.config\containers\

Describe the results you expected

Not ... this.

podman info output

OS: windows/amd64
provider: wsl
version: 5.1.0-rc1

Cannot connect to Podman. (I have the machine shut down at the moment.)

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

No

[Tyler-IN]

Upgraded to released v5.1.0, problem persists.

It is also checking in D:\etc and D:\usr\share\containers for some reason.

It appears to be discarding paths from the config, maybe needs a specific format... I'm going to try environment variables next.

[rhatdan]

Podman is searching for storage.conf in those directories. This should not be happening in Windows, but it is quite difficult to fix.

[ppoi]

5.0.3: ~\AppData\Roaming\containers 5.1.0: ~\AppData\Roamingcontainers

I think that 5.1.0's configuration folder path building process is wrong.

[Tyler-IN]

I investigated fixing it, fixed it in a local copy; mentioned the issue in https://github.com/containers/storage/issues/1943

Just needs to not use dumb paths on Windows and join paths with the right functions.

Might PR if I have time to ensure red tape is not an concern.

Hopefully you guys can fix it "the right way" though. 👍

[github-actions[bot]]

A friendly reminder that this issue had no activity for 30 days.