-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dockerfiles Ubuntu Xenial -> Bionic upgrade with python 3 #16
Conversation
…cript tries to install gnupg which isn't found in the repos
…ated in .welcome.sh
Thanks for the contribution. For the time being we want to keep Xenial as a default. It will probably be a while until we can switch a default base image (we will need to ensure Python 3 stuff on Bionic has been running without any issues on large production deployments for a while, etc.). The changes itself are good though and we should figure out how we can utilize them to allow people to test docker setup using Ubuntu Bionic as a base image. Perhaps it should be user configurable some how, or maybe we should build another set of test containers with Bionic as a base image? |
Yes, exactly what @Kami said. No quick plans in switching the base image, at least until we start supporting We're not eager to keep optional Bionic images or separated repo fork until that happens. |
base/Dockerfile
Outdated
@@ -32,7 +34,7 @@ ENV LANG='en_US.UTF-8' LANGUAGE='en_US:en' LC_ALL='en_US.UTF-8' | |||
|
|||
# Install StackStorm, but without UI | |||
RUN if [ "${ST2_VERSION#*dev}" != "${ST2_VERSION}" ]; then \ | |||
ST2_REPO=unstable; \ | |||
ST2_REPO=staging-unstable; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know the difference between unstable and staging-unstable. Is switching to staging-unstable still "valid" a year later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need unstable
.
See more info behind packaging repositories: https://github.com/StackStorm/discussions/wiki/Useful-info-for-Release-Managers#packagecloud-repositories
As a note, I build all of the containers using bionic and deployed into a kubernetes cluster. Everything seems to be working. One other Dockerfile to consider updating is st2chatops/Dockerfile.
|
@ytjohn Awesome, can you create a PR for st2chatops? |
Fixes Packagecloud add repo issue: ``` Package gnupg is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source Unable to install GPG! Your base system has a problem; please check your default OS's package repositories because GPG should work. Repository installation aborted. E: Package 'gnupg' has no installation candidate ```
@armab Thanks. I had created a downstream PR since I can't directly modify this one, but your pushes have incorporated them now. |
Cool, I think I'm going to merge this soon. The plan is to switch from
It will provide a migration path between the major versions. This means StackStorm installation in K8s HA will be py3-based only from that point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dswebbthg for the contribution and @ytjohn for testing & trying it!
Seemingly only a few changes needed for the migration to bionic, gnupg as a package can't be found so had to preinstall gpg, some changes to the .welcome.sh file to support python3. Added in a separate commit for the staging-unstable repo as this probably won't get merged.