WSL: [WSL1/2] Import error due to hard links
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
Please fill out the below information:
-
Your Windows build number: (Type
verat a Windows Command Prompt) -
What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.) Version 1803 build 18970
-
What’s wrong / what should be happening instead: When loading Clearlinux rootfs.tar on WSL 1 and 2, it ends abruptly with
unexpected errorinstead of loading the distro. -
For WSL launch issues, please collect detailed logs. wslcl.zip
Attached are the 3 log files, and here is a sample of the error: sbin: Hard-link target ‘bin’ does not exist. usr/bin/b2sum: Hard-link target ‘usr/bin/[’ does not exist. usr/bin/base32: Hard-link target ‘usr/bin/[’ does not exist. usr/bin/base64: Hard-link target ‘usr/bin/[’ does not exist. usr/bin/basename: Hard-link target ‘usr/bin/[’ does not exist. usr/bin/basenc: Hard-link target ‘usr/bin/[’ does not exist. usr/bin/bzcat: Hard-link target ‘usr/bin/bunzip2’ does not exist. usr/bin/bzfgrep: Hard-link target ‘usr/bin/bzegrep’ does not exist.
the hard links come from the fact that Clearlinux uses coreutils in the default bundle os-core
While the executables can be copied instead of the hard links, the libraries have the same setup (/lib points to /usr/lib).
I do have Clearlinux in WSL1 since the build 18305, but even if I export and import it again, it will also fail.
Thanks in advance for your help 😃
WSL Corsair
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 18 (1 by maintainers)
I experienced the same. I did:
gem cleanup --dryrunandgem cleanupapt remove rubyrm -rf /home/$USER/gemsThat did it for me:
for i in $(gem list | awk {'print $1'}); do gem uninstall $i -ax --force; done@haakoo : I got very similar errors also all in
/rdocrelated to Ruby.Logging into WSL to remove ruby manually and trying again… WORKED FOR ME
Even after uninstalling as many of the gems as I could (some were default; using
--forceper @Eyal51 would likely have fixed that), I was still having trouble. I ultimately just did asudo apt uninstall rubyandrm -rf /var/lib/gems. That fixed it for me, and setting the WSL version of the Ubuntu app to 2 gave me back Ruby anyway.ok so I had to reinstall ruby, and then tried cleaning up rdoc, power_assert, net-telnet, minitest, and fileutils. That didn’t work, so then I uninstalled them with
gem uninstall.That didn’t work either, then I noticed that the error message actually changed a bit:
So now I’m trying to the uninstall etc, did_you_mean, csv, bigdecimal gems and see how that works.
edit - that worked! so basically I checked the error message for ruby gems causing the problem, and iteratively removed gems until I was able to fix it.
Is there any update to this? I have the same problem.
I’m getting this same error now, after “GA”.
Any ideas, or should I just delete it and start over fresh? Any steps I can do to get better debug data?