Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export Warning/Error #12454

Open
1 of 2 tasks
godreborn opened this issue Jan 12, 2025 · 3 comments
Open
1 of 2 tasks

Export Warning/Error #12454

godreborn opened this issue Jan 12, 2025 · 3 comments
Assignees

Comments

@godreborn
Copy link

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Nov 5 00:21:55 UTC 2024

Distro Version

Arch

Other Software

No response

Repro Steps

I'm trying to export Arch and Ubuntu 22.04, both give similar errors (I have six distros altogether, and only these two have these messages): Export in progress, this may take a few minutes.: ./etc/pacman.d/gnupg/S.dirmngr: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.extra: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.ssh: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.browser: pax format cannot archive sockets...

I think this has something to do with keys. ubuntu 22.04 mentions similar but with devkitpro key files. I've never had this happen in all my years of exporting wsl, and I have no idea how to correct it or if I should even ignore it.

Expected Behavior

it should have success with no messages like the one above.

Actual Behavior

./etc/pacman.d/gnupg/S.dirmngr: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.extra: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.ssh: pax format cannot archive sockets: ./etc/pacman.d/gnupg/S.gpg-agent.browser: pax format cannot archive sockets...

Diagnostic Logs

I'm not sure how to do this.

Copy link

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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!

Closed similar issues:

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

@godreborn
Copy link
Author

WslLogs-2025-01-12_17-00-24.zip

I'm not sure if I did this correctly. I couldn't allow the export to go through. it created the zip once I copied and pasted the initial command.

Copy link

Diagnostic information
Detected appx version: 2.3.26.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants