From be54c87aaff8c1671dce8387f5879acd29fe9e09 Mon Sep 17 00:00:00 2001 From: Etienne Perot Date: Wed, 14 Aug 2024 15:42:51 -0700 Subject: [PATCH] Update FAQ to reflect that ARM64 is fully supported. PiperOrigin-RevId: 663080476 --- g3doc/user_guide/FAQ.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/g3doc/user_guide/FAQ.md b/g3doc/user_guide/FAQ.md index 693fab721..0d29b5cda 100644 --- a/g3doc/user_guide/FAQ.md +++ b/g3doc/user_guide/FAQ.md @@ -8,9 +8,8 @@ Today, gVisor requires Linux. ### What CPU architectures are supported? {#supported-cpus} -gVisor currently supports [x86_64/AMD64](https://en.wikipedia.org/wiki/X86-64) -compatible processors. Preliminary support is also available for -[ARM64](https://en.wikipedia.org/wiki/ARM_architecture#AArch64). +gVisor supports [x86_64/AMD64](https://en.wikipedia.org/wiki/X86-64) and +[ARM64](https://en.wikipedia.org/wiki/ARM_architecture#AArch64) processors. ### Do I need to modify my Linux application to use gVisor? {#modify-app} @@ -60,7 +59,7 @@ This is tracked in [bug #268](https://gvisor.dev/issue/268). You're using an old version of Docker. See [Docker Quick Start][docker]. -### I can’t see a file copied with: `docker cp` {#fs-cache} +### I can't see a file copied with: `docker cp` {#fs-cache} For performance reasons, gVisor caches directory contents, and therefore it may not realize a new file was copied to a given directory. To invalidate the cache