Automated commit at Mon Apr 1 08:30:01 CEST 2024

This commit is contained in:
Mischa van den Burg 2024-04-01 08:30:01 +02:00
parent 54a9a52c90
commit 0ce881b120
4 changed files with 34 additions and 1 deletions

View File

@ -0,0 +1,14 @@
When you build an image locally using `docker build` it will be added to the image registry on your workstation.
You can pull it into the Rancher Desktop Kubernetes cluster as follows:
`kubectl run zk --image=zettelkasten-server:latest --image-pull-policy=Never`
The image pull policy of Never will prevent the kubelet from trying to pull the image. You are giving the instruction that the image is somehow already present, and this is true because it's available in the Rancher Desktop registry. Pretty clean. And it is a nice workflow in my opinion.
## Links:
202404010807

View File

@ -0,0 +1,17 @@
Must include `
```bash
docker build --platform amd64 .
```
or add this in dockerfile
```yaml
FROM --platform=amd64 debian
...
```
## Links:
[creating amd64 docker image on m1 - Stack Overflow](https://stackoverflow.com/questions/68881910/creating-amd64-docker-image-on-m1)
202403311844

View File

@ -1,6 +1,9 @@
[[Managing permissions for GitHub Container Registry]]
[[Building docker images on Mac M1 - M2 - Silicon]]
[[Rancher Desktop]]
## Links:

View File

@ -11,5 +11,4 @@ The reasoning behind this is that the brain needs to be trained to exclusively a
## Links:
202404010724