Deferred path resolution during container deployment

US11775475B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11775475-B2
Application numberUS-201916293456-A
CountryUS
Kind codeB2
Filing dateMar 5, 2019
Priority dateMar 5, 2019
Publication dateOct 3, 2023
Grant dateOct 3, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques of deferred container deployment are disclosed herein. In one embodiment, a method includes receiving, at a computing device, a container image corresponding to the container. The container image includes a first set of files identified by symbolic links individually directed to a file in the host filesystem on the computing device and a second set of files identified by hard links. The method also includes in response to receiving the container image, at the computing device, storing the received container image in a folder of the host filesystem on the computing device without resolving the symbolic links of the first set of the files until runtime of the requested container.

First claim

Opening claim text (preview).

We claim: 1. A method performed in a computing device having a processor, a storage device, and a memory containing instructions executable by the processor to provide a host filesystem, the method comprising: receiving, at the computing device, a container image corresponding to a container to be instantiated at the computing device to execute a container process, the container image including a first set of files identified by symbolic links individually directed to a file in the host filesystem on the computing device and a second set of files identified by hard links to files in the host filesystem; in response to receiving the container image, at the computing device, instantiating the container by: storing the first set of files in the container image in a folder of the host filesystem on the computing device without resolving the symbolic links until runtime of the container; and establishing the hard links corresponding to the second set of files in the container image; and during execution of the container process in the container after instantiating the container: receiving, at the host filesystem, a first file request from the container process for a first file included in the first set of files of the container image of the container; in response to receiving the first file request for the first file, at the host filesystem, determining whether a path of the first file included in the container image contains a symbolic link having a parent identifier and a first relative path; in response to determining that the path of the first file contains the symbolic link: consulting a table accessible by the host filesystem on the computing device, the table storing a unique identifier for the parent identifier and a corresponding parent path as entries, the unique identifier identifying the parent path; resolving the parent identifier by using the unique identifier to obtain the parent path; concatenating the first relative path to the parent path to obtain a full path corresponding to the first file; retrieving, from the storage device, a copy of the first file according to the full path; and serving the copy of the first file to the container process; and receiving, at the host filesystem, a second file request from the container process for a second file included in the container image, the second file being identified by the parent identifier and a second relative path that is different from the first relative path. 2. The method of claim 1 wherein: the parent identifier includes a globally unique identification string; and resolving the parent identifier includes identifying a corresponding file directory on the computing device by consulting the table accessible by the host filesystem. 3. The method of claim 1 , further comprising in response to determining that the path of the first file does not contain a symbolic link, locating a copy of the first file from the container image on the computing device and serving the copy of the first file to the container process. 4. The method of claim 1 wherein: the container image is stored on the computing device in a folder of the host filesystem; and the method further includes, in response to determining that the path of the first file does not contain a symbolic link, locating a copy of the first file from the folder containing the container image and serving the retrieved copy of the first file to the container process. 5. The method of claim 1 wherein: the container image is stored on the computing device in a folder of the host filesystem, the folder having multiple files. 6. The method of claim 1 wherein: the container image is stored on the computing device in a folder of the host filesystem, the folder having multiple files including the first file identified by the symbolic link and other files identified by additional symbolic links; and the method further includes not resolving any of the additional symbolic links to the other files until another file request from the container process for another one of the other files is received. 7. The method of claim 1 wherein: the parent identifier is a first parent identifier; the method further includes receiving, at the host filesystem, a third file request from the container process for a third file included in the container image, the third file being identified by the parent identifier and a third relative path; and the third relative path is different from the first relative path. 8. The method of claim 1 wherein: the parent identifier is a first parent identifier; the method further includes receiving, at the host filesystem, a third file request from the container process for a third file included in the container image, the third file being identified by the parent identifier and a third relative path; and the third relative path is not different from the first relative path. 9. The method of claim 1 wherein: the parent identifier is a first parent identifier; the method further includes receiving, at the host filesystem, a third file request from the container process for a third file included in the container image, the third file being identified by a second parent identifier and a third relative path; and the second parent identifier is different than the first parent identifier while the third relative path is the same as the first relative path. 10. A computing device, comprising: a processor; a storage device; and a memory containing instructions executable by the processor to provide a host filesystem and to cause the computing device to: receive, at the computing device, a container image corresponding to a container to be instantiated at the computing device to execute a container process, the container image including a first set of files identified by symbolic links individually directed to a file in the host filesystem on the computing device and a second set of files identified by hard links to files in the host filesystem; in response to receiving the container image, at the computing device, instantiating the container, wherein instantiating the container causes the computing device to: store the first set of files in the container image in a folder of the host filesystem on the computing device without resolving the symbolic links until runtime of the container; and establish the hard links corresponding to the second set of files; and during execution of the container process in the container after instantiating the container: upon receiving, at the host filesystem, a first file request from the container process for a first file included in the first set of files of the container image: determine whether a path of the first file included in the container image contains a symbolic link having a parent identifier and a first relative path; in response to determining that the path of the first file contains the symbolic link:  consulting a table accessible by the host filesystem on the computing device, the table storing a unique identifier for the parent identifier and a corresponding parent path as entries, the unique identifier identifying the parent path;  resolve the parent identifier by using the unique identifier to obtain the parent path;  concatenate the first relative path to the parent path to obtain a full path corresponding to the first file; and  retrieve, from the storage device, a copy of the first file according to the full path; and  serve the copy of the first file to the container process; and receiving, at the host filesystem, a second file request from the container process for a second file included in the container image, the second file being identified by the parent identifier and a second

Assignees

Inventors

Classifications

  • G06F16/128Primary

    Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16) · CPC title

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

  • Virtual file systems · CPC title

  • using directory or table look-up (use of a directory or look-up table in file systems G06F16/13) · CPC title

  • G06F9/455Primary

    Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11775475B2 cover?
Techniques of deferred container deployment are disclosed herein. In one embodiment, a method includes receiving, at a computing device, a container image corresponding to the container. The container image includes a first set of files identified by symbolic links individually directed to a file in the host filesystem on the computing device and a second set of files identified by hard links. …
Who is the assignee on this patent?
Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification G06F16/128. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Oct 03 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 11 related publications on this page (citations in our corpus or others sharing the same primary CPC).