From bbfb3c63eaf74ea63c440f06d4b55a0e5085ef38 Mon Sep 17 00:00:00 2001 From: Thomas McWork Date: Fri, 21 Mar 2025 17:47:59 +0100 Subject: [PATCH] docs: add instructions to find the docker group id to the compose docs --- .../content/docs/community-resources/docker-compose.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/src/content/docs/community-resources/docker-compose.mdx b/docs/src/content/docs/community-resources/docker-compose.mdx index 191048a..6b5bf9f 100644 --- a/docs/src/content/docs/community-resources/docker-compose.mdx +++ b/docs/src/content/docs/community-resources/docker-compose.mdx @@ -1,3 +1,5 @@ +import { Callout } from "nextra/components"; + # Docker Compose Many users find it useful to run Cup with Docker Compose, as it enables them to have it constantly running in the background and easily control it. Cup's lightweight resource use makes it ideal for this use case. @@ -40,4 +42,8 @@ Cup can run with a non-root user, but needs to be in a docker group. Assuming us user: "1000:999" ``` -The compose can be customized further of course, if you choose to use a different port, another config location, or would like to change something else. Have fun! \ No newline at end of file + +You can use the command `getent group docker | cut -d: -f3` to find the group id for the docker group. + + +The compose can be customized further of course, if you choose to use a different port, another config location, or would like to change something else. Have fun!