gilles/scrutiny
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update TROUBLESHOOTING_DOCKER.md

Browse Source
This commit is contained in:
Jason Kulatunga
2022-06-09 07:35:07 -07:00
committed by GitHub
parent 453069deec
commit 7ba7b6efda
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/TROUBLESHOOTING_DOCKER.md
+3 -3
View File
@@ -1,5 +1,8 @@
# Docker Images `master-omnibus` vs `latest` # Docker Images `master-omnibus` vs `latest`
> TL;DR; The `master-omnibus` and `latest` tags are almost semantically identical, as I follow a `golden master`
development process. However if you want to ensure you're only using the latest release, you can change to `latest`
The CI script used to orchestrate the docker image builds can be found here: https://github.com/AnalogJ/scrutiny/blob/master/.github/workflows/docker-build.yaml#L166-L184 The CI script used to orchestrate the docker image builds can be found here: https://github.com/AnalogJ/scrutiny/blob/master/.github/workflows/docker-build.yaml#L166-L184
In general Scrutiny follows a `golden master` development process, which means that the `master` branch is not directly updated (unless its for documentation changes), In general Scrutiny follows a `golden master` development process, which means that the `master` branch is not directly updated (unless its for documentation changes),
@@ -20,6 +23,3 @@ ignored -- https://github.com/AnalogJ/scrutiny/issues/287. That has since been f
Hope that gives you an understanding for how everything is wired up. Hope that gives you an understanding for how everything is wired up.
TL;DR; The `master-omnibus` and `latest` tags are almost semantically identical, as I follow a `golden master`
development process. However if you want to ensure you're only using the latest release, you can change to `latest`