From mboxrd@z Thu Jan 1 00:00:00 1970 References: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com> From: Zdenek Kabelac Message-ID: <7839ff52-18e5-6a95-9a2a-12ea73457700@redhat.com> Date: Thu, 11 Apr 2019 13:32:15 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: Eric Ren Cc: LVM general discussion and development , thornber@redhat.com, lvm-devel@redhat.com Dne 11. 04. 19 v 13:26 Eric Ren napsal(a): > Hi=C2=A0Zdenek, >=20 > Thanks for your reply. The use case is for containerd snapshooter, yes, a= ll=20 > lvm setup is on host machine, creating thin LV for VM-based/KATA containe= r as=20 > rootfs. >=20 > For example: > https://github.com/containerd/containerd/pull/3136 >=20 > and >=20 > https://github.com/containerd/containerd/pull/3022 >=20 > So, we're evaluating such solution now~ >=20 Hi I could recommend to orient towards the solution where the 'host' system=20 provides some service for your containers - so container ask for action,=20 service orchestrates the action on the system - and returns asked resource = to=20 the container. IMHO I don't see any other usable solution ATM - although many container=20 developers seems to endlessly try to run these system commands from a conta= iner... Regards Zdenek