From 6e2e7413306041209b748a2c5e4238581551249e Mon Sep 17 00:00:00 2001 From: Zihao Zhou Date: Tue, 15 Oct 2024 18:22:05 -0700 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9B=20Fix=20link?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/guide/limit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/limit.md b/docs/guide/limit.md index a6c2692..bbe2ccb 100644 --- a/docs/guide/limit.md +++ b/docs/guide/limit.md @@ -72,7 +72,7 @@ It is technically feasible to create a Docker container inside your container, b > LXC upstream's position is that those containers aren't and cannot be root-safe. They are still valuable in an environment where you are running trusted workloads or where no untrusted task is running as root in the container. —— [Linux Containers - LXC - Security](https://linuxcontainers.org/lxc/security/) -Our position is Docker-based development should be deployed to the Nautilus cluster. However, you may request privilege on a short term basis with valid reason (e.g., to build a Docker image for your accepted paper). However, docker overlay2 storage driver [does not work well with LXC](https://discuss.linuxcontainers.org/t/problem-running-docker-inside-lxc-container/10392), so you may need to downgrade docker to 2.3.0 in order to use the removed `overlay` driver. See [Troubleshooting](/troubleshooting.md) for more information. +Our position is Docker-based development should be deployed to the Nautilus cluster. However, you may request privilege on a short term basis with valid reason (e.g., to build a Docker image for your accepted paper). However, docker overlay2 storage driver [does not work well with LXC](https://discuss.linuxcontainers.org/t/problem-running-docker-inside-lxc-container/10392), so you may need to downgrade docker to 2.3.0 in order to use the removed `overlay` driver. See [Troubleshooting](./troubleshooting) for more information. ## Firewall