[
https://issues.apache.org/jira/browse/DISPATCH-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909043#comment-17909043
]
ASF GitHub Bot commented on DISPATCH-2357:
------------------------------------------
jiridanek opened a new pull request, #1726:
URL: https://github.com/apache/qpid-dispatch/pull/1726
We need to use supported CentOS. In newer CentOS Streams, the PowerTools
repo was renamed to crb (same name as in RHEL). Using Rocky Linux 8 seems most
sensible, as we are not ready to upgrade all the way to CentOS 9 or 10.
The Dockerfile was initially intended as a help for development, not really
a release artifact. If a development Dockerfile is needed, it can be added in
the future.
Meanwhile, using development versions of software at random places, which
then becomes part of our release tar.gz, creates bad impression and should be
eliminated.
As a compromise, the Dockerfile can use the contents of the local directory
for Dispatch sources. In a released tar.gz, that would be the released content,
so we're fine there.
> Don't clone git tips in Dockerfile
> ----------------------------------
>
> Key: DISPATCH-2357
> URL: https://issues.apache.org/jira/browse/DISPATCH-2357
> Project: Qpid Dispatch
> Issue Type: Sub-task
> Affects Versions: 1.19.0
> Reporter: Jiri Daněk
> Assignee: Jiri Daněk
> Priority: Major
> Fix For: 1.20.0
>
>
> Building the dockerfile from an release archive should result in a container
> image that uses released components, not current upstream checkout.
> Currently, the container clones main branches of qpid-dispatch and
> qpid-proton during container build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
