Skip to content

Commit fdaaa3c

Browse files
authored
Merge pull request #622 from Mossaka/bump-rust-1.79
chore: bump rust to 1.79
2 parents 12fd000 + 97da9a6 commit fdaaa3c

File tree

2 files changed

+3
-7
lines changed

2 files changed

+3
-7
lines changed

crates/containerd-shim-wasm/README.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,7 @@ A library to help build containerd shims for wasm workloads.
1010
use containerd_shim as shim;
1111
use containerd_shim_wasm::sandbox::{ShimCli, Instance, Nop}
1212

13-
fn main() {
14-
shim::run::<ShimCli<Nop>>("io.containerd.nop.v1", opts);
15-
}
13+
shim::run::<ShimCli<Nop>>("io.containerd.nop.v1", opts);
1614
```
1715

1816
The above example uses the built-in `Nop` instance which does nothing.
@@ -30,9 +28,7 @@ impl Instance for MyInstance {
3028
// ...
3129
}
3230

33-
fn main() {
34-
shim::run::<ShimCli<MyInstance>>("io.containerd.myshim.v1", opts);
35-
}
31+
shim::run::<ShimCli<MyInstance>>("io.containerd.myshim.v1", opts);
3632
```
3733

3834
containerd expects the shim binary to be installed into `$PATH` (as seen by the containerd process) with a binary name like `containerd-shim-myshim-v1` which maps to the `io.containerd.myshim.v1` runtime which would need to be configured in containerd. It (containerd) also supports specifying a path to the shim binary but needs to be configured to do so.

rust-toolchain.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
[toolchain]
2-
channel="1.78.0"
2+
channel="1.79.0"
33
profile="default"
44
targets = ["wasm32-wasi"]

0 commit comments

Comments
 (0)