Deprecate all-in-one Docker #191
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
transhapHigsn
pushed a commit
to DiligenceVault/st2-docker
that referenced
this pull request
Jun 8, 2021
…e-docker Deprecate all-in-one Docker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This all-in-one Docker demo deployment wasn't supported for a long time, was missing expected development/maintenance effort with no contributors and is deprecated now.
Latest StackStorm release that supported all-in-one docker was
v3.1.0based onUbuntu Trustywithpython 2. As we deprecated Ubuntu Trusty, there are no all-in-one Docker images deploys for later st2 releases.There is a
docker-composealternative based onst2-dockerfilesimages based onUbuntu:bionicandpython 3with better security and following Docker best practices, see:StackStorm/st2-dockerfiles#28
It will replace the
st2-dockercontents soon, while current codebase will be archived into a dedicatedDEPRECATED-all-in-onebranch. With that change, bothK8sanddocker-composedeployments will eventually use the same https://github.com/StackStorm/st2-dockerfiles/ images.