[Issue] Odd tarball layout on Windows platform when exporting image by regctl #786
Description
Current Behavior
Using regctl to export image on Windows outputs a odd tarball.
Expected Behavior
Got a normal tar file.
Steps To Reproduce
Running the following commands on Windows (every image will reproduce this behavior, nginx is just an example), then verify the tar file.
.\regctl-windows-amd64.exe image export -p "linux/amd64" library/nginx:latest nginx-linux-amd64.tarReviewing the tar file with 7-Zip:
7-Zip 24.04 (x64) : Copyright (c) 1999-2024 Igor Pavlov : 2024-04-05
Scanning the drive for archives:
1 file, 70987264 bytes (68 MiB)
Listing archive: .\nginx-linux-amd64.tar
--
Path = .\nginx-linux-amd64.tar
Type = tar
Physical Size = 70987264
Headers Size = 7680
Code Page = UTF-8
Characteristics = POSIX ASCII
Date Time Attr Size Compressed Name
------------------- ----- ------------ ------------ ------------------------
1970-01-01 08:00:00 ..... 30 512 oci-layout
1970-01-01 08:00:00 ..... 367 512 index.json
1970-01-01 08:00:00 ..... 2350 2560 manifest.json
1970-01-01 08:00:00 D.... 0 0 blobs_sha256
1970-01-01 08:00:00 ..... 2295 2560 blobs_sha256_db5e49f40979ce521f05f0bc9f513d0abacce47904e229f3a95c2e6d9b47f244
1970-01-01 08:00:00 ..... 7296 7680 blobs_sha256_fffffc90d343cbcb01a5032edac86db5998c536cd0a366514121a45c6723765c
1970-01-01 08:00:00 ..... 29126278 29126656 blobs_sha256_f11c1adaa26e078479ccdd45312ea3b88476441b91be0ec898a7e07bfd05badc
1970-01-01 08:00:00 ..... 41833344 41833472 blobs_sha256_c6b156574604a095a5847d3b34cf36d484bb49862365e996b391d0ba0f345034
1970-01-01 08:00:00 ..... 628 1024 blobs_sha256_ea5d7144c337402f813ea7c05c11dab58b7841f4c41fb5f5058abefbc2451ec5
1970-01-01 08:00:00 ..... 955 1024 blobs_sha256_1bbcb9df2c93e03db739f7e49ce73eda0325b8087ef8e88386d303d883c357ab
1970-01-01 08:00:00 ..... 393 512 blobs_sha256_537a6cfe3404285310129c72dfc3f352e7c5db1a5f296e514d739322bab5a998
1970-01-01 08:00:00 ..... 1209 1536 blobs_sha256_767bff2cc03ef46478039907c5bca487eb27d5f43a38571985e4ed4dc0403d5a
1970-01-01 08:00:00 ..... 1398 1536 blobs_sha256_adc73cb74f2591613c7c88f7f6a313c3373bbfa3bda0983677bb233668b4033a
------------------- ----- ------------ ------------ ------------------------
1970-01-01 08:00:00 70976543 70979584 12 files, 1 folders
It shows that the folder was not be created correctly.
But it seems like the docker (version 26.1.4) will accept such tar file anyway.
Version
VCSTag: v0.7.0
VCSRef: 3e517a07d79f8a863cf39b78934935cdcb35f65f
VCSCommit: 3e517a07d79f8a863cf39b78934935cdcb35f65f
VCSState: clean
VCSDate: 2024-07-12T18:40:58Z
Platform: windows/amd64
GoVer: go1.22.5
GoCompiler: gc
Environment
- Running as binary or container: binary
- Host platform: Windows
- Registry description: Docker Hub