podman-machine-default.json gets corrupted on improper Windows shutdown #18011
Description
Issue Description
The file C:\Users\<username>\.config\containers\podman\machine\wsl\podman-machine-default.json gets corrupted (basically filled with a bunch of NULLs) on an improper Windows shutdown, like a BSOD. I had like three of them due to debugging a driver project and the json file got consistently corrupted despite me not using any podman command or changed anything in Podman Desktop during the session.
Steps to reproduce the issue
Steps to reproduce the issue
- Simply set up podman on Windows as per guide
- Crash the system (e.g. using NotMyFault)
- After a reboot, podman won't work anymore due to corrupted
podman-machine-default.json
Describe the results you received
Podman is basically completely dead until it is re-initialized.
Describe the results you expected
I'd like to understand how a file that is not actively written to during the crash can get mangled so badly.
podman info output
host:
arch: amd64
buildahVersion: 1.29.0
cgroupControllers:
- cpuset
- cpu
- cpuacct
- blkio
- memory
- devices
- freezer
- net_cls
- perf_event
- net_prio
- hugetlb
- pids
- rdma
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: conmon-2.1.5-1.fc36.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.5, commit: '
cpuUtilization:
idlePercent: 99.91
systemPercent: 0.07
userPercent: 0.02
cpus: 16
distribution:
distribution: fedora
variant: container
version: "36"
eventLogger: journald
hostname: BLYAT-PC
idMappings:
gidmap: null
uidmap: null
kernel: 5.10.102.1-microsoft-standard-WSL2
linkmode: dynamic
logDriver: journald
memFree: 53134725120
memTotal: 53831020544
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.8.1-1.fc36.x86_64
path: /usr/bin/crun
version: |-
crun version 1.8.1
commit: f8a096be060b22ccd3d5f3ebe44108517fbf6c30
rundir: /run/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +WASM:wasmedge +YAJL
os: linux
remoteSocket:
exists: true
path: /run/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: false
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-0.2.beta.0.fc36.x86_64
version: |-
slirp4netns version 1.2.0-beta.0
commit: 477db14a24ff1a3de3a705e51ca2c4c1fe3dda64
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 13958643712
swapTotal: 13958643712
uptime: 0h 28m 16.00s
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /usr/share/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mountopt: nodev,metacopy=on
graphRoot: /var/lib/containers/storage
graphRootAllocated: 269490393088
graphRootUsed: 815177728
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "true"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /run/containers/storage
transientStore: false
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 4.4.1
Built: 1676629882
BuiltTime: Fri Feb 17 11:31:22 2023
GitCommit: ""
GoVersion: go1.18.10
Os: linux
OsArch: linux/amd64
Version: 4.4.1Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes