@@ -27,7 +27,7 @@ The extension always detects (because its exit code is `0`) and provides a depen
27
27
cat $PWD /samples/extensions/curl/bin/generate
28
28
```
29
29
30
- The extension generates a ` run.Dockerfile ` that switches the run image to reference ` run-image-curl ` .
30
+ The extension generates a ` run.Dockerfile ` that switches the run image to reference ` localhost:5000/ run-image-curl` .
31
31
32
32
### Build a run image for ` curl ` extension to use
33
33
@@ -114,7 +114,7 @@ curl 7.85.0-DEV (x86_64-pc-linux-musl) ... more stuff here ...
114
114
What happened: now that ` hello-extensions ` requires both ` tree ` and ` curl ` in its build plan, both extensions are
115
115
included in the build and provide the needed dependencies for build and launch, respectively
116
116
* The ` tree ` extension installs ` tree ` at build time, as before
117
- * The ` curl ` extension switches the run image to ` run-image-curl ` , which has ` curl ` installed
117
+ * The ` curl ` extension switches the run image to ` localhost:5000/ run-image-curl` , which has ` curl ` installed
118
118
119
119
Now our ` curl ` process can succeed!
120
120
@@ -132,7 +132,7 @@ You should see:
132
132
ERROR: failed to launch: path lookup: exec: "cowsay": executable file not found in $PATH
133
133
```
134
134
135
- Our run image, ` run-image-curl ` , has ` curl ` installed, but it doesn't have ` cowsay ` .
135
+ Our run image, ` localhost:5000/ run-image-curl` , has ` curl ` installed, but it doesn't have ` cowsay ` .
136
136
137
137
In general, we may not always have a preconfigured run image available with all the needed dependencies for the current application.
138
138
Luckily, we can also use image extensions to dynamically install runtime dependencies at build time. Let's look at that next.
0 commit comments