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

can not chroot to centos6 rootfs #5465

Closed
zltl opened this issue Jun 23, 2020 · 3 comments
Closed

can not chroot to centos6 rootfs #5465

zltl opened this issue Jun 23, 2020 · 3 comments

Comments

@zltl
Copy link

zltl commented Jun 23, 2020

Environment

My Windows build number:

PS C:\Users\liaot> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

My Distribution version:
Ubuntu Release: 20.04

cat /proc/version:
Linux version 4.4.0-18362-Microsoft ([email protected]) (gcc version 5.4.0 (GCC) ) #836-Microsoft Mon May 05 16:04:00 PST 2020

Steps to reproduce

  1. Download a centos6 rootfs from https://github.com/CentOS/sig-cloud-instance-images/tree/CentOS-6.10/docker

  2. Extract it on wsl:

mkdir -p /fakeroot/c6
cp /path/to/centos-6-docker.tar.xz /fakeroot/c6
cd /fakeroot/c6
tar -xpf centos-6-docker.tar.xz  --numeric-owner
chroot /fakeroot/c6

Expected behavior

chroot to /fakeroot/c6

Actual behavior

Segmentation fault (core dumped)
@zltl
Copy link
Author

zltl commented Jun 23, 2020

Then I try centos7 rootfs and gentoo stage3, chroot work well both.

chroot to Centos6 rootfs work on real linux.

@therealkenc
Copy link
Collaborator

138   rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
138   --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffffffffff600400} ---

chroot to Centos6 rootfs work on real linux.

That depends on the disposition of the Real Linux in question about vsyscalls.

/dupe #4694 (message) aka #1462

@ghost
Copy link

ghost commented Jun 23, 2020

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@ghost ghost added the duplicate label Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants