[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[atomic-devel] We are looking at using OSTree as a backend for sharing file systems into an OCID Container runtime
- From: Daniel J Walsh <dwalsh redhat com>
- To: Colin Walters <walters redhat com>, Vivek Goyal <vgoyal redhat com>, Vincent Batts <vbatts redhat com>
- Cc: "Temple, William M" <wmtemple wpi edu>, "atomic-devel projectatomic io" <atomic-devel projectatomic io>
- Subject: [atomic-devel] We are looking at using OSTree as a backend for sharing file systems into an OCID Container runtime
- Date: Fri, 14 Oct 2016 14:37:07 -0400
We are seeing the same problem that William Temple had this summer,
where OSTree refuses to store an image with devices on it. We
understand that devices should not be in image, but sadly Ubuntu image
has them and therefore thousands of other images do as well.
If we block the creation of the devices when exploding a OCI Image
Bundle, we end up with something that is different then what is
downloaded and this could potentially cause problems with mtree checking
of the image on disk versus the image as shipped.
Is there a reason OSTree does not work with Device Inodes?
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]