use cnoe/tools-image #179
use cnoe/tools-image #179
Conversation
Signed-off-by: Jesse Sanford <[email protected]>
|
@nabuskey what do you think about this. I can clean up the commented out debug lines if you think this is a good idea. I don't see why we wouldn't just build an image? |
|
I didn't want to maintain a docker image so I just used a script to do it. Do we have automations around this? We should also keep set e and x. When people have problems with this script, I'd hate to troubleshoot without them. |
| @@ -205,7 +205,7 @@ spec: | |||
| name: config-job | |||
| containers: | |||
| - name: kubectl | |||
| image: docker.io/library/ubuntu:22.04 | |||
| image: ghcr.io/cnoe-io/tools-image:latest | |||
There was a problem hiding this comment.
The github repository which is hosting the code of the container image is empty https://github.com/cnoe-io/tools-image. Is it a mistake ? Do you plan to push the code within the repo ?
|
I am also on the side of not wanting to maintain an image for internal tools. We already added documentation on core packages and their versions. I am proposing that this issue can be closed. |
|
Closing this since we moved our examples to the stacks repo. Please reopen in that repo if this is still relevant. |
Proposing we build an image rather than install stuff at runtime.