[
https://issues.apache.org/jira/browse/IMPALA-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8622:
----------------------------------
Description:
Some consumers of the Impala docker images will want to publish them to a repo.
Currently they would have to hardcode a list of the docker images produced by
the Impala build to publish them, or do something brittle like "docker image
ls" to deduce what images were built.
It would be useful if the build produced a list of the images in some
consumable format that would be updated (either manually or automatically) when
the set of images changes. If it needs to be manually updated, we should have
some kind of check to verify that it isn't stale.
One option is to produce JSON, something like:
{noformat}
{
“docker_images”: {
“impala_base”: “$docker_registry/impala_base”,
” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
....
}
}
{noformat}
was:
Some consumers of the Impala docker images will want to publish them to a repo.
Currently they would have to hardcode a list of the docker images produced by
the Impala build to publish them, or do something brittle like "docker image
ls" to deduce what images were built.
It would be useful if the build produced a list of the images in some
consumable format that would be updated (either manually or automatically) when
the set of images changes. If it needs to be manually updated, we should have
some kind of check to verify that it isn't stale.
> Generate list of docker images generated by the build
> -----------------------------------------------------
>
> Key: IMPALA-8622
> URL: https://issues.apache.org/jira/browse/IMPALA-8622
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: docker
>
> Some consumers of the Impala docker images will want to publish them to a
> repo. Currently they would have to hardcode a list of the docker images
> produced by the Impala build to publish them, or do something brittle like
> "docker image ls" to deduce what images were built.
> It would be useful if the build produced a list of the images in some
> consumable format that would be updated (either manually or automatically)
> when the set of images changes. If it needs to be manually updated, we should
> have some kind of check to verify that it isn't stale.
> One option is to produce JSON, something like:
> {noformat}
> {
> “docker_images”: {
> “impala_base”: “$docker_registry/impala_base”,
> ” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
> ....
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
