Abstract: An example method for filesystem pass-through on lightweight virtual machine containers includes executing a container on a host, and creating a file system overlay in a local file system storage located on the host. The example method further includes copying files and directories into the file system overlay from a shared file system until the file system overlay is fully populated. The file system overlay is fully populated when all the files and directories from the shared file system are copied into the file system overlay. Once fully populated, completion is marked which indicates the file system overlay is fully populated, where marking the completion prevents accessing a read-only base image within the shared file system.

Abstract: An example method for filesystem pass-through on lightweight virtual machine containers includes executing a container on a host, and creating a file system overlay in a local file system storage located on the host. The example method further includes copying files and directories into the file system overlay from a shared file system until the file system overlay is fully populated. The file system overlay is fully populated when all the files and directories from the shared file system are copied into the file system overlay. Once fully populated, completion is marked which indicates the file system overlay is fully populated, where marking the completion prevents accessing a read-only base image within the shared file system.

Abstract: An example method for filesystem pass-through on lightweight virtual machine containers includes executing a container on a host, and creating a file system overlay in a local file system storage located on the host. The example method further includes copying files and directories into the file system overlay from a shared file system until the file system overlay is fully populated. The file system overlay is fully populated when all the files and directories from the shared file system are copied into the file system overlay. Once fully populated, completion is marked which indicates the file system overlay is fully populated, where marking the completion prevents accessing a read-only base image within the shared file system.

Abstract: Some examples of the present disclosure relate to container-image replication. One example includes a computing device that can generate a container image. The container image can include metadata that is consumable by a container engine for deploying a container with settings specified in the metadata. The computing device can also generate provenance data indicating at least one aspect related to the generation of the container image. The computing device can modify the metadata in the container image to include an indicator of the provenance data. The computing device can then store the container image and the provenance data in one or more repositories accessible to a client device. This may enable the client device to reproduce the container image at a future point in time.

Abstract: Some examples of the present disclosure relate to container-image replication. One example includes a computing device that can generate a container image. The container image can include metadata that is consumable by a container engine for deploying a container with settings specified in the metadata. The computing device can also generate provenance data indicating at least one aspect related to the generation of the container image. The computing device can modify the metadata in the container image to include an indicator of the provenance data. The computing device can then store the container image and the provenance data in one or more repositories accessible to a client device. This may enable the client device to reproduce the container image at a future point in time.

Abstract: Disclosed herein is technology to capture and distribute a state of a file system that updates, removes, or adds a computer program to a computing device. An example method may include: analyzing a program package associated with a plurality of objects of a computer program; determining a state of a file system after an installation of the program package; generating a manifest that corresponds to the computer program and represents the state of the file system after the installation, the manifest comprising a hash tree that comprises object identification data of an object of the plurality of objects of the computer program; and providing the manifest to one or more computing devices.

Abstract: Mechanisms for disassembling and reassembling a tar archive are disclosed. A computing device accesses a tar archive comprising a file payload data segment and a plurality of non-payload data segments. The non-payload data segments in the tar archive are identified. The non-payload data segments are stored in a replay log structure. The file payload data segment of a file is identified in the tar archive, and file identification data identifying the file is stored in the replay log structure. The file payload data segment is not stored in the replay log structure.

Abstract: Some examples of the present disclosure relate to container-image replication. One example includes a computing device that can generate a container image. The container image can include metadata that is consumable by a container engine for deploying a container with settings specified in the metadata. The computing device can also generate provenance data indicating at least one aspect related to the generation of the container image. The computing device can modify the metadata in the container image to include an indicator of the provenance data. The computing device can then store the container image and the provenance data in one or more repositories accessible to a client device. This may enable the client device to reproduce the container image at a future point in time.

Abstract: An example method for filesystem pass-through on lightweight virtual machine containers includes executing a container on a host, and creating a file system overlay in a local file system storage located on the host. The example method further includes copying files and directories into the file system overlay from a shared file system until the file system overlay is fully populated. The file system overlay is fully populated when all the files and directories from the shared file system are copied into the file system overlay. Once fully populated, completion is marked which indicates the file system overlay is fully populated, where marking the completion prevents accessing a read-only base image within the shared file system.

Abstract: Disclosed herein is technology to capture and distribute a state of a file system that updates, removes, or adds a computer program to a computing device. An example method may include: analyzing a program package associated with a plurality of objects of a computer program; determining a state of a file system after an installation of the program package; generating a manifest that corresponds to the computer program and represents the state of the file system after the installation, the manifest comprising a hash tree that comprises object identification data of an object of the plurality of objects of the computer program; and providing the manifest to one or more computing devices.

Abstract: Mechanisms for disassembling and reassembling a tar archive are disclosed. A computing device accesses a tar archive comprising a file payload data segment and a plurality of non-payload data segments. The non-payload data segments in the tar archive are identified. The non-payload data segments are stored in a replay log structure. The file payload data segment of a file is identified in the tar archive, and file identification data identifying the file is stored in the replay log structure. The file payload data segment is not stored in the replay log structure.