Skip to content

Commit 178a7a3

Browse files
authored
Merge pull request #10819 from afbjorklund/image-docs
Add basic documentation for minikube image command
2 parents 45f76a9 + 5919ee7 commit 178a7a3

File tree

1 file changed

+33
-1
lines changed

1 file changed

+33
-1
lines changed

site/content/en/docs/handbook/pushing.md

Lines changed: 33 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Pushing images"
33
weight: 5
44
description: >
5-
comparing 6 ways to push your image into a minikube cluster.
5+
comparing 8 ways to push your image into a minikube cluster.
66
aliases:
77
- /docs/tasks/building
88
- /docs/tasks/caching
@@ -21,6 +21,8 @@ Here is a comparison table to help you choose:
2121
| [docker-env command](/docs/handbook/pushing/#1pushing-directly-to-the-in-cluster-docker-daemon-docker-env) | only docker | good |
2222
| [podman-env command](/docs/handbook/pushing/#3-pushing-directly-to-in-cluster-crio-podman-env) | only cri-o | good |
2323
| [buildctl command](/docs/handbook/pushing/#6-pushing-directly-to-in-cluster-containerd-buildkitd) | only containerd | good |
24+
| [image load command](/docs/handbook/pushing/#7-loading-directly-to-in-cluster-container-runtime) | all | ok |
25+
| [image build command](/docs/handbook/pushing/#8-building-images-to-in-cluster-container-runtime) | all | ok |
2426
| [cache add command]({{< ref "/docs/commands/cache.md#minikube-cache-add" >}}) | all | ok |
2527
| [registry addon](/docs/handbook/pushing/#4-pushing-to-an-in-cluster-using-registry-addon) | all | ok |
2628
| [minikube ssh](/docs/handbook/pushing/#5-building-images-inside-of-minikube-using-ssh) | all | best |
@@ -300,3 +302,33 @@ buildctl --addr unix://buildkitd.sock build \
300302
```
301303

302304
now you can 'build' against the storage inside minikube. which is instantly accessible to kubernetes cluster.
305+
306+
---
307+
308+
## 7. Loading directly to in-cluster container runtime
309+
310+
The minikube client will talk directly to the container runtime in the
311+
cluster, and run the load commands there - against the same storage.
312+
313+
```shell
314+
minikube image load my_image
315+
```
316+
317+
For more information, see:
318+
319+
* [Reference: image load command]({{< ref "/docs/commands/image.md#minikube-image-load" >}})
320+
321+
---
322+
323+
## 8. Building images to in-cluster container runtime
324+
325+
The minikube client will talk directly to the container runtime in the
326+
cluster, and run the build commands there - against the same storage.
327+
328+
```shell
329+
minikube image build -t my_image .
330+
```
331+
332+
For more information, see:
333+
334+
* [Reference: image build command]({{< ref "/docs/commands/image.md#minikube-image-build" >}})

0 commit comments

Comments
 (0)