runsc install -> panic: Only 4K page size is supported on arm64!

[yizhaohuipg13]

Description

/usr/local/bin/runsc install
panic: Only 4K page size is supported on arm64!

goroutine 1 [running]:
gvisor.dev/gvisor/pkg/hostarch.init.0()
	pkg/hostarch/hostarch_arm64.go:59 +0x48

Is this feature related to a specific bug?

No response

Do you have a specific solution in mind?

Regarding the support on arm64, can the community support pagesize of 64k or other sizes in the future, please

[github-actions[bot]]

A friendly reminder that this issue had no activity for 120 days.

[flokli]

Ran into this today, while trying to execute something on Asahi Linux (on a MacBook, which has non-4K pagesize).

[sduqlsc]

same here, with kylin linux 4.19.90-52.39.v2207.ky10.aarch64

[sduqlsc]

seems hv to compile kernel source to modify page_size

[sduqlsc]

stil no reply

[tranji-cloud]

Hello sduqlsc,

Thanks for the ping, I will look at this soon.

[molinzhifeng]

Hello, I have also encountered the same issue. May I ask if it can be resolved

[sduqlsc]

Hello sduqlsc,

Thanks for the ping, I will look at this soon.

Great, hope it worked on arm64, it would save me a lot of time.

[sduqlsc]

any info update? or is there a guid to manually compile on arm64? @tranji-cloud

[avagin]

any info update? or is there a guid to manually compile on arm64? @tranji-cloud

To compile it, you just need to have docker on your arm64 machine, and then make runsc should build the runsc binary for you (https://github.com/google/gvisor?tab=readme-ov-file#building)

Regarding your question about updates, we don't have any current plans to add support for non-4k page size setups. However, we'd gladly accept a pull request if you or someone else implements it.

As a workaround, you can recompile and install a linux kernel with 4k pages.

[sduqlsc]

any info update? or is there a guid to manually compile on arm64? @tranji-cloud

To compile it, you just need to have docker on your arm64 machine, and then make runsc should build the runsc binary for you (https://github.com/google/gvisor?tab=readme-ov-file#building)

Regarding your question about updates, we don't have any current plans to add support for non-4k page size setups. However, we'd gladly accept a pull request if you or someone else implements it.

As a workaround, you can recompile and install a linux kernel with 4k pages.

so i recomplie it on 64K kernel, simply using go, seems not run successfully, if just comment panic statment.

docker run --rm --runtime=runsc hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
198f93fd5094: Pull complete 
Digest: sha256:a0dfb02aac212703bfcb339d77d47ec32c8706ff250850ecc0e19c8737b18567
Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: creating container: cannot create sandbox: cannot read client sync file: waiting for sandbox to start: EOF: unknown

[avagin]

so i recomplie it on 64K kernel, simply using go, seems not run successfully, if just comment panic statment.

You need to recompile a kernel with 4K pages. Is there any real reason to use the 64K page size?

[sduqlsc]

so i recomplie it on 64K kernel, simply using go, seems not run successfully, if just comment panic statment.

You need to recompile a kernel with 4K pages. Is there any real reason to use the 64K page size?

client's OS distribution is 64K...