Skip to content
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

Replace ubuntu focal with jammy #70

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NitinNahal
Copy link

Replace ubuntu focal with jammy

  • Update Dockerfiles for ubuntu jammy for base/ , st2chatops/ and st2web/ components

  • Correct staging package source

  • Update nodesource setup version in st2chatops, compatible with jammy

- Update Dockerfiles for ubuntu jammy
  for base/ , st2chatops/ and st2web/
  components

- Correct staging package source

- Update nodesource setup version
  in st2chatops, compatible with
  jammy
@CLAassistant
Copy link

CLAassistant commented Jan 29, 2025

CLA assistant check
All committers have signed the CLA.

@nzlosh
Copy link
Contributor

nzlosh commented Feb 4, 2025

Will this change the OS for container build for St2 v3.8?

@NitinNahal
Copy link
Author

NitinNahal commented Feb 10, 2025

Will this change the OS for container build for St2 v3.8?

Hello @nzlosh , I have not much idea on how the release process of containers are running but i think there should be a tag mechanism for the release which obviously should depend on the ST2 version being used as ARG - https://github.com/StackStorm/st2-dockerfiles/blob/cebea8dd374fbca30b1974b7c33e8adfd99116e8/base/Dockerfile#L5C5-L5C16 , what do you think ?

Also if you notice the new images get the tag - https://app.circleci.com/pipelines/github/StackStorm/st2-dockerfiles/1994/workflows/164f38f9-72e4-4db9-a64b-1448e96d0b5f/jobs/2527

REPOSITORY                                   TAG                 IMAGE ID            CREATED              SIZE
stackstorm/st2web                            3.9dev              9ea43a83b34d        1 second ago         185MB
stackstorm/st2chatops                        3.9dev              2e0c58128ee8        32 seconds ago       494MB
stackstorm/st2actionrunner                   3.9dev              9948c9ac76a2        About a minute ago   588MB
stackstorm/st2notifier                       3.9dev              099eae53bfad        2 minutes ago        577MB
stackstorm/st2scheduler                      3.9dev              5d6447776843        2 minutes ago        577MB
stackstorm/st2sensorcontainer                3.9dev              a4177311ec80        2 minutes ago        577MB
stackstorm/st2stream                         3.9dev              fce18673b761        2 minutes ago        577MB
stackstorm/st2                               3.9dev              6f2524b671dc        2 minutes ago        577MB
stackstorm/st2timersengine                   3.9dev              aa3a3c8629f8        2 minutes ago        577MB
stackstorm/st2auth                           3.9dev              1972faa7fbd2        2 minutes ago        577MB
stackstorm/st2rulesengine                    3.9dev              98e8d376a260        2 minutes ago        577MB
stackstorm/st2api                            3.9dev              fb865cb3371b        2 minutes ago        577MB
stackstorm/st2workflowengine                 3.9dev              4475e9cfcb17        2 minutes ago        577MB
stackstorm/st2garbagecollector               3.9dev              c4fd51efe30b        2 minutes ago        577MB
public.ecr.aws/eks-distro/kubernetes/pause   3.6                 3c69a9ca2c95        15 months ago        6.62MB
docker                                       18-git              796b9c4f0b4e        5 years ago          213MB

I dont see the v3.8 images being created every night here - https://app.circleci.com/pipelines/github/StackStorm/st2-dockerfiles . So how are they uploaded ? This change once merged, will mean that any new image build on master will have new OS yes but if the v3.8 images (prod) are not built with ever new merge to master, then it should be safe.

Please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants