In this Get Started guide you will learn:
This is the multi-page printable view of this section. Click here to print.
Getting Started
1 - Build your first 2DFS image
tdfs
Image Builder
tdfs
is a command-line tool that allows you to create and manage 2DFS images. It is designed to be simple and easy to use. All you need to do is install the utility, create your 2dfs.json
descriptor file, and run the tdfs build
command to create your first 2DFS image.
Installation
You can install the latest stable TDFS CLI builder using the following command:
curl -sfL 2dfs.github.io/install-tdfs.sh | sh -
Your first 2DFS image
Create your first 2DFS image by creating a 2dfs.json
descriptor file in the current directory.
For example, let’s create two simple files and add them to the 2dfs.json
descriptor file:
Create two sample files in the current directory:
touch file1.txt file2.txt
Now let’s create a 2dfs.json
descriptor file with the following content:
{
"allotments":[
{
"src":"./file1.txt",
"dst":"/file1.txt",
"row":0,
"col":0
},
{
"src":"./file2.txt",
"dst":"/file2.txt",
"row":0,
"col":1
}
]
}
This descriptor creates two allotements, one for each file, and places them respectively in the first row, columns 0 and 1 of the 2dfs.field
layer.
Once the 2dfs.json
descriptor file is created, you can run the tdfs build
command to create your first 2DFS image. In this example, we’ll start from a ubuntu:22.04
base image:
tdfs build ubuntu:22.04 myfirsttdfs:v1
This command will build a 2dfs.field
layer on top of the ubuntu:22.04
base image, for each supported architecture (amd64, arm64, etc.), and create a new 2DFS image named myfirsttdfs:v1
. The 2dfs.field
layer will contain the two files you specified in the 2dfs.json
descriptor file.
Optimize your build for specific OS/Architecture combinations
To build an image specific for an OS/Architecture combination, please use the --platforms
flag. E.g., tdfs build --platform linux/amd64,linux/arm64 ubuntu:22.04 myfirsttdfs:v1
If the build is successful, you can now check the new 2DFS image by running the following command:
tdfs image ls
The output should look like this:
Url Tag Type Reference --------------------------------------------------------------------------------------------------------- 0 docker.io/library/ubuntu:22.04 22.04 OCI 12fac12bf3f369441a389d8947acc9c7a81bfd018e24aa8fedc0407845f59b87 1 docker.io/library/myfirsttdfs:v1 v1 OCI+2DFS 9e376e53b46e6c7ce79c3a8b5cd73382db345e3b410fce8ae62b2f3e54c7d149
You should see both the base image and the new 2DFS image in the list, one with the OCI
and the other with type OCI+2DFS
.
Note
Check all the available commands usingtdfs -h
2 - Create and use your 2DFS Image Registry
The 2DFS Image Registry is a container registry that supports OCI
and OCI+2DFS
images.
It is built on top of the OCI Distribution Specification.
Deploy the 2DFS Image Registry as a container
Use Docker to deploy the 2DFS Image Registry as a container:
docker run -d -p 5000:5000 --restart=always --name 2dfs-registry ghcr.io/2dfs/2dfs-registry:edge
This will create the registry and expose it on port 5000
.
For more details and configuration options, refer to the 2DFS Registry GitHub Repository.
Push your first 2DFS image to your registry
Assuming the registry is running locally (address 0.0.0.0:5000
), let’s build a simple 2DFS image and push it to your registry.
tdfs build ubuntu:22.04 0.0.0.0:5000/test/myfirsttdfs:v1
With this command, we created an image named myfirsttdfs
belonging to the repository test
of the registry 0.0.0.0:5000
, tagged with v1
.
The output of tdfs image ls
should look like this:
Url Tag Type Reference --------------------------------------------------------------------------------------------------------- ... 12 0.0.0.0:5000/test/myfirsttdfs:v1 v1 OCI+2DFS 9e376e53b46e6c7ce79c3a8b5cd73382db345e3b410fce8ae62b2f3e54c7d149
Now we can push the image to the registry:
tdfs push 0.0.0.0:5000/test/myfirsttdfs:v1
This command will push the myfirsttdfs:v1
image to the test
repository of the registry 0.0.0.0:5000
.
3 - Retrieve 2DFS Images from Docker
When using a local registry, you need to configure Docker to trust the local insecure registry.
To do this, use the following configuration for your Docker daemon configuration file (usually located at /etc/docker/daemon.json
):
{
"features": {
"containerd-snapshotter": true
},
"insecure-registries": [
"<your-registry-host>:5000"
]
}
Replace <your-registry-host>
with the hostname or IP address of your registry.
To retrieve a 2DFS image from a Docker registry, you can use the docker pull
command. This command allows you to download images from a registry that supports the OCI+2DFS format.
Additionally, you can use a semantic tag in the form --<row from>.<col from>.<row to>.<col to>
to define the partition of the image you want to pull.
Let’s say we pushed to our registry an OCI+2DFS
image with 2 rows and 2 columns, like this:
Row/Col | Col 0 | Col 1 |
---|---|---|
Row 0 | file1.txt | file2.txt |
Row 1 | file3.txt | file4.txt |
If we want to pull the first element of the first row (file1.txt
), we can use the following command:
docker pull <your-registry-host>:5000/test/myfirsttdfs:v1--0.0.0.0
To retrieve the entire image as OCI image, you can use the following command:
docker pull <your-registry-host>:5000/test/myfirsttdfs:v1--0.0.1.1
To retrieve all elements except for file3.txt
, you can use the following command:
docker pull <your-registry-host>:5000/test/myfirsttdfs:v1--0.0.0.1--1.0.1.1