@@ -78,8 +78,6 @@ GO111MODULE=on make all
78
78
Once you have built the runtime, be sure to place the following binaries on your
79
79
` $PATH ` :
80
80
* ` runtime/containerd-shim-aws-firecracker `
81
- * ` snapshotter/cmd/devmapper/devmapper_snapshotter `
82
- * ` snapshotter/cmd/naive/naive_snapshotter `
83
81
* ` firecracker-control/cmd/containerd/firecracker-containerd `
84
82
* ` firecracker-control/cmd/containerd/firecracker-ctr `
85
83
@@ -135,10 +133,11 @@ root = "/var/lib/firecracker-containerd/containerd"
135
133
state = " /run/firecracker-containerd"
136
134
[grpc ]
137
135
address = " /run/firecracker-containerd/containerd.sock"
138
- [proxy_plugins ]
139
- [proxy_plugins .firecracker-devmapper ]
140
- type = " snapshot"
141
- address = " /var/run/firecracker-containerd/devmapper-snapshotter.sock"
136
+ [plugins ]
137
+ [plugins .devmapper ]
138
+ pool_name = " fc-dev-thinpool"
139
+ base_image_size = " 10GB"
140
+ root_path = " /var/lib/firecracker-containerd/snapshotter/devmapper"
142
141
143
142
[debug ]
144
143
level = " debug"
@@ -153,7 +152,7 @@ binaries are in sync with one another. While other builds of `ctr` may work with
153
152
### Prepare and configure snapshotter
154
153
155
154
The devmapper snapshotter requires a thinpool to exist.
156
- Below is a script to create a thinpool as well as an example config file .
155
+ Below is a script to create a thinpool device .
157
156
158
157
` Note: The configuration with loopback devices is slow and not intended for use in production. `
159
158
205
204
```
206
205
</details >
207
206
208
- <details >
209
- <summary >Snappshotter config file example.</summary >
210
-
211
- ``` json
212
- {
213
- "base_image_size" : " 10GB" ,
214
- "root_path" : " /var/lib/firecracker-containerd/snapshotter/devmapper" ,
215
- "pool_name" : " fc-dev-thinpool"
216
- }
217
- ```
218
-
219
- </details >
220
-
221
- A reasonable location for this file is at ` /etc/firecracker-dm-snapshotter/config.json ` .
222
-
223
207
### Configure containerd runtime plugin
224
208
225
209
The runtime expects a JSON-formatted configuration file to be located either in
@@ -277,17 +261,7 @@ configuration file has the following fields:
277
261
278
262
## Usage
279
263
280
- Start the containerd snapshotter
281
-
282
- ``` bash
283
- $ ./devmapper_snapshotter \
284
- -address /var/run/firecracker-containerd/devmapper-snapshotter.sock \
285
- -path /tmp/fc-snapshot \
286
- -config /etc/firecracker-dm-snapshotter/config.json
287
- ```
288
- ` note: The path for -config needs to match the location used when configuring the devmapper snapshotter. `
289
-
290
- In another terminal, start containerd
264
+ Start containerd
291
265
292
266
``` bash
293
267
$ sudo PATH=$PATH /usr/local/bin/firecracker-containerd \
@@ -298,15 +272,17 @@ Pull an image
298
272
299
273
``` bash
300
274
$ sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock images \
301
- pull --snapshotter firecracker- devmapper\
275
+ pull --snapshotter devmapper \
302
276
docker.io/library/busybox:latest
303
277
```
304
278
305
279
And start a container!
306
280
307
281
``` bash
308
282
$ sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock \
309
- run --snapshotter firecracker-devmapper --runtime aws.firecracker \
283
+ run \
284
+ --snapshotter devmapper \
285
+ --runtime aws.firecracker \
310
286
--rm --tty --net-host \
311
287
docker.io/library/busybox:latest busybox-test
312
288
```
@@ -321,7 +297,7 @@ $ sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock \
321
297
$ sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock \
322
298
namespaces label fc \
323
299
containerd.io/defaults/runtime=aws.firecracker \
324
- containerd.io/defaults/snapshotter=firecracker- devmapper
300
+ containerd.io/defaults/snapshotter=devmapper
325
301
326
302
$ sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock \
327
303
-n fc \
0 commit comments