-
Select Topic AreaGeneral BodyHey guys, I was wondering for best practices with Github actions. Currently I made an action which is defined via For situations like this, where the image does not need to "be updated" on every run, is it better to have it built into a docker image and then make the step use the image directly? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
@ckcr4lyf One way to use a pre-built image is to push the image to a container registry, such as Docker Hub, and then use the uses syntax in the workflow file to reference the image. This way, the image is only built when you update it and pushed to the container registry. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I am able to use pre built images, I was just wondering what the "better" approach is, use a pre-built, or have GH actions build it for every run. Seems the default to publish a docker actions is have it build every time |
Beta Was this translation helpful? Give feedback.
-
|
building the image every time on GitHub Actions can ensure that you always have the latest versions of dependencies and security patches, but it can also increase the time and resource usage. It depends on your use case and resources, you can use a pre-built image and update them regularly or you can use GitHub Actions to build the image every time. |
Beta Was this translation helpful? Give feedback.
-
|
Got it, there are tradeoffs on either side. Thanks for explaining, I will mark it as solved |
Beta Was this translation helpful? Give feedback.
-
It would be excellent to provide an example of this syntax... Here: And... In the hello world repo, add a workflow file that uses both the "build each time" and the "use existing image" path, for example: https://github.com/actions/hello-world-docker-action/blob/main/action.yml#L13 |
Beta Was this translation helpful? Give feedback.
@ckcr4lyf One way to use a pre-built image is to push the image to a container registry, such as
Docker Hub, and then use the uses syntax in the workflow file to reference the image.
This way, the image is only built when you update it and pushed to the container registry.