You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(where x is the next version number for the container)
51
+
52
+
53
+
When the build completes you'll see the following warning:
54
+
55
+
> WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
56
+
57
+
It's important you don't restart your docker build container before you load and/or push since it may blow away the cache you need to push or load from.
58
+
59
+
### Load
60
+
Currently you can't use --load with docker desktop so the only way to test the container is to rebuild for one platform only:
This will be operating off of the cache so it shouldn't take very long to complete. After it does you'll see your image using the classic `docker images` command. Now you can login to the container to test it out:
47
67
48
68
```bash
49
69
docker run --rm -it -v ${PWD}:/repo ghcr.io/opencyphal/toxic:tx22.4.x
70
+
```
71
+
72
+
### Push
73
+
74
+
As with load, you need to re-build with a `--push` argument but you'll be using the cache so the build should be a no-op:
The two commands above make some assumptions about defaults and capabilities that we haven't verified on all build hosts. First, the `buildx create` command is assumed to target the correct Docker context. You can see your contexts by doing:
83
+
84
+
```
85
+
docker context ls
86
+
```
87
+
88
+
... then target a specific context by adding it as an additional argument to the builder create command:
We also assume you are using a build that has our two supported host platforms `linux/amd64` and `linux/arm64`. You can verify this after creating the builder using the inspect command. This should also verify that your builder is now in effect:
0 commit comments