search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.42k stars 822 forks source link

Exporting distribution problem #12193

Open foundnom opened 1 week ago

foundnom commented 1 week ago

Windows Version

Windows11 23H2 (22631.4317)

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu-22.04

Other Software

PowerShell 7.4.5

Repro Steps

wsl --shutdown
wsl --export Ubuntu-22.04 D://test.tar

Expected Behavior

I'm expecting a success export.

Actual Behavior

When I'm trying to export my Ubuntu-22.04 into a tar file, it shows info below:

..: ./root/.cache/at-spi/bus_0: pax format cannot archive sockets: ./root/.gnupg/S.gpg-agent.ssh: pax format cannot archive sockets: ./root/.gnupg/S.gpg-agent.browser: pax format cannot archive sockets: ./root/.gnupg/S.gpg-agent: pax format cannot archive sockets: ./root/.gnupg/S.gpg-agent.extra: pax format cannot archive socke.

Diagnostic Logs

No response

github-actions[bot] commented 1 week ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

tcostermans commented 1 week ago

I'm facing the same issue. I think the export is still running. You can monitor it using ls from powershell fe. It will take some time (minutes) before the file size increases.

I also got the warnings but in the end I got: "The operation completed successfully."

"pax format cannot archive sockets" => I think you should see this as a warning. The mentioned file will not be part of the backup. Chatgpt feedback: The pax format does not support archiving Unix domain sockets. This limitation is because Unix domain sockets are not regular files and are typically used for inter-process communication (IPC), not for data storage. ;-)

benhillis commented 1 week ago

@foundnom - could you please try removing those sockets and trying to export again?

mgua commented 4 days ago

I got a similar issue:

wsl --export u2404_usb \\docs\aimodels\temp\u2404cuda12.6.1-docker-kaldi.tar Export in progress, this may take a few minutes.: ./tmp/tmux-0/default: pax format cannot archive sockets

In my case the problem was caused by wrongly closed tmux sessions. I interrupted the export, reconnected to the wsl, executed shutdown -h now, then repeated the export, and did not get the error.