Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 1186822581C for <~alpine/users@lists.alpinelinux.org>; Tue, 9 Dec 2025 09:34:00 +0000 (UTC) Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-594270ec7f9so5915952e87.3 for <~alpine/users@lists.alpinelinux.org>; Tue, 09 Dec 2025 01:34:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765272838; x=1765877638; darn=lists.alpinelinux.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lLfw2e12XLfSHqBLszjYauhbsbi4DKR+BTasc/7O2Ok=; b=U9/wLgjDiLE66pLz+zRXJ1zK5QpQq2E6f+Ah43mcf6Ggd89yD5an5KVn05x6zMDSMo ftpnCIkI6Qr7BfK9UWm/htIdx1zvkV9FpbiMelgwXjr8Qs4TikkMmWtxQL8NBDWJ+g4t yfEv9krN1d5inC38vaR7p4f3irIaW2yi5e8UCinvLrKTp6LaS9N46CntmgtV9Rd9nWNy PqMso30wKtNzBwWDh0sEWSKeyf7NCwdOWh3PYeQYx6MTmc4g5UZFXFEnSTdsRv63B8nf oYlZk2csXUbIJLA1ffg2366qGV8xwgWzIx4EWg4ZaBooKyuFI19QonhW4zcJwUppaBDr sAfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765272838; x=1765877638; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=lLfw2e12XLfSHqBLszjYauhbsbi4DKR+BTasc/7O2Ok=; b=ubSgyjpVDwUDDhegH48HnPPPz512Iu2ZjvH+5AWg2DKdVAR4I8D6jPL1+jmEZQGRWF N012LJYWOTHmkp/Qho+3CI0Jy4IIE3KSIPP+uzWkq8iINEmYl7NHjPIlDK/yVyuBd8Bu 6HpLGnX0MMrVDfVQfYVO3ImtzzoJAtZFwrYQonjIoSOTRECsDZhYKfko0D8qUBRyFbt/ ZZ0f+P3JFcqS+AzeS7+lgRcqBosaVTMpe+U4dAWRRnWUGM6McbDIthflUe6BOByNA2ch CTUZ/buFIEd1l5cgvmvt3jnHwNPIXSmQ/+9iv9s27tMIW84Oz6cKCfJWyiQ3ov1UiulR ocqQ== X-Gm-Message-State: AOJu0YzvsvjwzjrTRzemhzjWTLs8scsLzrzDZ6DafWRoxm4TfOIvxdG1 kNTqp/sClalsT6z6sB+ZWNHCCxY3KdhMTg+Dx2vNTEIij+V6sCUE7K1sxO7FhEPCUqRa9acFzvJ EMwDLjnbQVjZRq4KqGBqFEpoyVbZh/g== X-Gm-Gg: ASbGncuP/0iNiI55i0rtOQzecq7ZMYuUR0TqvJiPX1mPuo96TILdEvZXQesoeHtDoU0 s9e33U/Jk4ibpmmaywmh3G8IhmwjwrmBBlLu8X8CXoxg5RktHQV5gDPs3eN5N6yTVofL1z4kNNN dBdTHSiwipvo9rCrSeqcf0rQPVFdUYR8mDpQpgzSIsTar5Fd2cCl7qw5mLc/DGlW1cz41dhOPwC Nb9FkXSgfPC7GCvk2ZNOB7qoi/2BbgZZpXq2PSaGkh8M+bZN8FoC7hIfenDxGZhXb5gduOd36Lu xZ0CA46oBxVQGuEKMYzYEluMiBQ= X-Google-Smtp-Source: AGHT+IFZ5tRZSnFUP7vk7jIKMSmglz0FMnsRTu8D83MESDa4C/C7mUWVTZEY7oLJUob+DzA5CNuque+P64bR6Paio54= X-Received: by 2002:a05:6512:138d:b0:594:2eee:dc9 with SMTP id 2adb3069b0e04-5987e8a713amr3344567e87.18.1765272837272; Tue, 09 Dec 2025 01:33:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jerome Marc Date: Tue, 9 Dec 2025 10:33:43 +0100 X-Gm-Features: AQt7F2rB-iFGE8-oyjdWvmEsFgcJigz5RsJ0T1orXvhUdoMlNAww80HyBUoINz4 Message-ID: Subject: Re: running containers (Podman or Docker) in diskless mode ? To: Guido Trotter Cc: ~alpine/users@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000065b95b0645819c7d" --00000000000065b95b0645819c7d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I need an image. There is no problem running the process inside the container in a read-only root. There are options for that. But even if the guest is read-only, it doesn't mean that the container host can use a ro filesystem. I guess that lxc could be more flexible for that. Le mar. 9 d=C3=A9c. 2025 =C3=A0 08:24, Guido Trotter = a =C3=A9crit : > If you're running just a container it should depend on what process you > run in the container... You wouldn't need to run "the os" necessarily, so > using read only would work if your process never writes to disk. In some > cases you might not need an os image at all. > > On Tue, 9 Dec 2025, 01:26 Jerome Marc, wrote: > >> Hello, >> >> I would like to deploy a small container on my RPI. >> The OS is running in diskless mode (lbu) and I have a quite large data >> partition which is read-only. >> I use the data partition to store large stuff like node libraries. >> >> By the way I was expecting to be able to start a container from this >> read-only partition. As the container is immutable I don't see any reaso= n >> to make the partition rw, except of course when updating the docker imag= e. >> So does anyone tried (and hopefully succeeded) to run a container that w= ay ? >> >> Thank you. >> >> >> --00000000000065b95b0645819c7d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I need an image. There is no problem running the process i= nside the container in a read-only root. There are options for that. But ev= en if the guest is read-only, it doesn't mean that=C2=A0the container h= ost can use a ro filesystem. I guess that lxc could be more flexible for th= at.

Le=C2=A0mar. 9 d=C3=A9c. 2025 =C3=A0=C2=A008:24, G= uido Trotter <ultrotter@debian.o= rg> a =C3=A9crit=C2=A0:
If you're running just a container it = should depend on what process you run in the container... You wouldn't = need to run "the os" necessarily, so using read only would work i= f your process never writes to disk. In some cases you might not need an os= image at all.

On Tue, 9 Dec 2025, 01:26 Jerome Marc, <marcgruselle@gmail.com> = wrote:
Hello,

I would like to deploy a small conta= iner on my RPI.
The=C2=A0OS is running in diskless mode (lbu) and= I have a quite=C2=A0large data partition which is read-only.
I u= se the data partition to store large stuff=C2=A0like node libraries.
<= div>
By the way I was expecting to be able to start a contain= er from this read-only partition. As the container is immutable I don't= see any reason to make the partition rw, except of course when updating th= e docker image. So does anyone tried (and hopefully succeeded) to run a con= tainer that way ?

Thank you.

<= div>
--00000000000065b95b0645819c7d--