# US 2021/0240671 A1 · Intelligent filesystem for container images

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0240671 A1
- Document ID: US20210240671A1
- Status: Published application
- Kind: A1
- Application number: 16/778,896
- Filed: 2020-01-31
- Published: 2021-08-05
- Earliest claimed: 2020-01-31
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC IP Holding Company LLC
- Inventors: Victor Fong; Kenneth Durazzo; Xuebin He
- Web page: https://patentgrep.com/patent/US20210240671A1

## CPC

- G06F 16/183: {Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097)}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 16/172: Caching, prefetching or hoarding of files
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

One example method includes transmitting a request for a container image to a registry, receiving metadata associated with the container image, wherein the metadata allows a controller to mount an empty filesystem on a host machine, starting a container from the container image without receiving all files associated with the container image, receiving files, from a container server, needed by the container based on an access sequence associated with the container. This allows a container to be started without downloading the entire container image and also conversed bandwidth by providing the files as needed based on the manner in which the container accesses files during execution.

## Claims

### Claim 1

A method, comprising:
transmitting a request for a container image to a registry;
receiving metadata associated with the container image, wherein the metadata allows a controller to mount an empty filesystem on a host machine;
starting a container from the container image without receiving all files associated with the container image;
receiving files, from a container server, needed by the container based on an access sequence associated with the container.

### Claim 2 (depends on 1)

The method of claim 1, further comprising determining the access sequence for the container based on a simulation of the container at the registry.

### Claim 3 (depends on 1)

The method of claim 1, further comprising caching the container image at the host machine.

### Claim 4 (depends on 1)

The method of claim 1, further comprising logging file accesses by the container at the host machine, wherein file accesses are added to the access sequence.

### Claim 5 (depends on 1)

The method of claim 1, further comprising tracking file accesses by the container through a container lifetime.

### Claim 6 (depends on 1)

The method of claim 1, further comprising executing the container without having all files associated with the container.

### Claim 7 (depends on 1)

The method of claim 1, further comprising flattening the container image for transfer, wherein files not identified in the access sequence are not transmitted to the controller.

### Claim 8 (depends on 1)

The method of claim 1, further comprising mounting a remote filesystem to facilitate transmitting files for the container based on the access sequence.

### Claim 9 (depends on 1)

The method of claim 1, further comprising determining whether the container image or any layers thereof are cached at the host machine.

### Claim 10 (depends on 1)

The method of claim 1, further comprising receiving a startup package that includes files for the container at startup.

### Claim 11

A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
transmitting a request for a container image to a registry;
receiving metadata associated with the container image, wherein the metadata allows a controller to mount an empty filesystem on a host machine;
starting a container from the container image without receiving all files associated with the container image;
receiving files, from a container server, needed by the container based on an access sequence associated with the container.

### Claim 12 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising determining the access sequence for the container based on a simulation of the container at the registry.

### Claim 13 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising caching the container image at the host machine.

### Claim 14 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising logging file accesses by the container at the host machine, wherein file accesses are added to the access sequence.

### Claim 15 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising tracking file accesses by the container through a container lifetime.

### Claim 16 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising executing the container without having all files associated with the container.

### Claim 17 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising flattening the container image for transfer, wherein files not identified in the access sequence are not transmitted to the controller.

### Claim 18 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising mounting a remote filesystem to facilitate transmitting files for the container based on the access sequence.

### Claim 19 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising determining whether the container image or any layers thereof are cached at the host machine.

### Claim 20 (depends on 11)

The non-transitory storage medium of claim 11, the operations further comprising receiving a startup package that includes files for the container at startup.
