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
Do not pin invocation image to a specific debian release (getporter#2745)
* Do not pin invocation image to a specific debian release
Use stable instead of a specific debian release, so that when the release is archived, we don't end up with an unbuildable bundle. If a user wants to pin to a base image, they should use a custom Dockerfile. Porter should default to a release (stable) that will always work, so that porter doesn't need to be recompiled or a new version installed because a debian release was archived.
Signed-off-by: Carolyn Van Slyck <[email protected]>
* Use golang:latest for our (defunct) developer workshop
Update the Porter workshop images to use golang:latest so that we don't need to keep updating it when it works just fine with any version of Go.
Signed-off-by: Carolyn Van Slyck <[email protected]>
---------
Signed-off-by: Carolyn Van Slyck <[email protected]>
Copy file name to clipboardexpand all lines: docs/content/blog/docker-mixin-blog-post.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Run Whalesay
106
106
Now, we will go through an example of how you can incorporate and build your own Docker image and then push it to Docker hub. First, you will need to create a Dockerfile named Dockerfile-cookies next to your porter.yaml and copy paste the code below into the file.
107
107
108
108
```
109
-
FROM debian:stretch-slim
109
+
FROM debian:stable-slim
110
110
111
111
CMD ["echo", "Everyone loves cookies"]
112
112
```
@@ -176,7 +176,7 @@ After it runs, you should see output that the image was built and tagged success
0 commit comments