Sharing filesystems between containers

Patent metadata

Field	Value
Publication number	US-11537652-B2
Application number	US-202117141261-A
Country	US
Kind code	B2
Filing date	Jan 5, 2021
Priority date	Jun 20, 2017
Publication date	Dec 27, 2022
Grant date	Dec 27, 2022

Abstract

A filesystem can be shared between containers. For example, a computing device having a host filesystem can launch a first container from an image file. Launching the first container can include creating an initialization directory for the first container on the host filesystem. The initialization directory can include a filesystem to be shared between containers. Launching the first container can also include creating a first filesystem directory for the first container on the host filesystem and mounting the initialization directory to the first filesystem directory. The computing device can also launch a second container from the image file. Launching the second container can include creating a second filesystem directory for the second container on the host filesystem and mounting the initialization directory to the second filesystem directory to enable the second container to access the filesystem.

First claim

The invention claimed is:

1. A non-transitory computer-readable medium comprising program code that is executable by a processing device for causing the processing device to launch a first container and a second container on a same host from a same image file, wherein launching the first container and the second container on the same host from the same image file involves:
creating an initialization directory on the host, wherein the initialization directory includes a shareable filesystem;
creating a first filesystem directory on the host, the first filesystem directory corresponding to the first container and being separate from the initialization directory;
creating a second filesystem directory on the host, the second filesystem directory corresponding to the second container and being separate from the initialization directory;
mounting the initialization directory to the first filesystem directory and to the second filesystem directory to enable the first container and the second container to access the shareable filesystem, wherein the shareable filesystem is a root filesystem for the first container and the second container; and
executing the first container simultaneously with the second container on the host, the first container and the second container being configured to use the root filesystem concurrently with one another.

2. The non-transitory computer-readable medium of claim 1 , wherein:
the first container and the second container are read-only containers;
mounting the initialization directory to the first filesystem directory includes read-only bind mounting the initialization directory to the first filesystem directory; and
mounting the initialization directory to the second filesystem directory includes read-only bind mounting the initialization directory to the second filesystem directory.

3. The non-transitory computer-readable medium of claim 1 , further comprising program code that is executable by the processing device for causing the processing device to:
determine that the initialization directory exists on the host; and
based on determining that the initialization directory exists on the host, launch the second container at least in part by mounting the initialization directory to the second filesystem directory.

4. The non-transitory computer-readable medium of claim 1 , wherein the initialization directory comprises data other than the shareable filesystem for initializing the first container and the second container.

5. A system comprising:
a processing device; and
a memory device comprising instructions executable by the processing device for causing the processing device to launch at least two containers from a same image file on a same host such that the at least two containers are configured to share a filesystem, wherein launching the at least two containers from the same image file on the same host involves:
creating an initialization directory on a host filesystem of the host, wherein the initialization directory includes the filesystem, wherein the filesystem is a root filesystem for a first container and a second container of the at least two containers;
creating a first filesystem directory on the host filesystem, the first filesystem directory corresponding to the first container among the at least two containers and being separate from the initialization directory;
creating a second filesystem directory on the host filesystem, the second filesystem directory corresponding to the second container among the at least two containers and being separate from the initialization directory;
mounting the initialization directory to the first filesystem directory and to the second filesystem directory; and
executing the first container simultaneously with the second container on the host, the first container and the second container being configured to use the root filesystem concurrently with one another.

6. The system of claim 5 , wherein:
the first container and the second container are read-only containers;
mounting the initialization directory to the first filesystem directory includes read-only bind mounting the initialization directory to the first filesystem directory; and
mounting the initialization directory to the second filesystem directory includes read-only bind mounting the initialization directory to the second filesystem directory.

7. The system of claim 5 , wherein the memory device further comprises instructions executable by the processing device for causing the processing device to:
determine that the initialization directory exists on the host filesystem; and
based on determining that the initialization directory exists on the host filesystem, launch the second container from the image file at least in part by mounting the initialization directory to the second filesystem directory.

8. The system of claim 5 , wherein the memory device further comprises instructions executable by the processing device for causing the processing device to:
based on launching the first container, update a record to reflect that the first container is using the initialization directory; and
based on launching the second container, update the record to reflect that the second container is using the initialization directory.

9. A computer-implemented method comprising:
launching at least two containers on a same host from a same image file, wherein the at least two containers share a same initialization directory and a same root filesystem while the at least two containers are running on the same host, wherein launching the at least two containers on the same host involves:
creating an initialization directory on a host filesystem of the host, wherein the initialization directory includes a root filesystem to be shared among the at least two containers;
creating a first filesystem directory on the host filesystem, the first filesystem directory corresponding to a first container among the at least two containers and being separate from the initialization directory;
creating a second filesystem directory on the host filesystem, the second filesystem directory corresponding to a second container among the at least two containers and being separate from the initialization directory;
mounting the initialization directory to the first filesystem directory and to the second filesystem directory; and
executing the at least two containers simultaneously on the host, wherein the at least two containers use the root filesystem concurrently with one another.

10. The method of claim 9 , wherein:
the first container and the second container are read-only containers;
mounting the initialization directory to the first filesystem directory includes read-only bind mounting the initialization directory to the first filesystem directory; and
mounting the initialization directory to the second filesystem directory includes read-only bind mounting the initialization directory to the second filesystem directory.

11. The method of claim 9 , further comprising:
determining that the initialization directory exists on the host filesystem; and
based on determining that the initialization directory exists on the host filesystem, launching the second container at least in part by mounting the initialization directory to the second filesystem directory.

12. The method of claim 9 , further comprising:
based on launching the first container, updating a record to reflect that the first container is using the initialization directory; and
based on launching the second container, updating the record to reflect that the second container is using the initialization directory.

13. The method of claim 9 , furth

Assignees

• Red Hat Inc

Inventors

• Eder Jeremy
• Sandeen Eric
• Walsh Daniel
• Goyal Vivek

Classifications

• G06F16/13 Primary

  File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06) · CPC title

• G06F16/176

  Support for shared access to files; File sharing support · CPC title

• G06F16/51 Primary

  Indexing; Data structures therefor; Storage structures · CPC title