You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2026/04/20 08:22:00 UTC

[jira] [Updated] (TEZ-4700) [Cloud] Single image shared between AM and Task

     [ https://issues.apache.org/jira/browse/TEZ-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

László Bodor updated TEZ-4700:
------------------------------
    Fix Version/s: 1.0.0

> [Cloud] Single image shared between AM and Task
> -----------------------------------------------
>
>                 Key: TEZ-4700
>                 URL: https://issues.apache.org/jira/browse/TEZ-4700
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: László Bodor
>            Assignee: Raghav Aggarwal
>            Priority: Major
>             Fix For: 1.0.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> This is a follow-up after TEZ-4682. Similarly to Hive, the desired way to have a single Dockerfile and image, and let the entrypoint distinguish between them.
> Currently we have:
> {code}
> tez-dist/src/docker/tez-am/Dockerfile.am
> tez-dist/src/docker/tez-am/am-entrypoint.sh
> tez-dist/src/docker/tez-am/am.env
> tez-dist/src/docker/tez-am/build-am-docker.sh
> ...
> {code}
> ideally we would have:
> {code}
> tez-dist/src/docker/Dockerfile
> tez-dist/src/docker/am-entrypoint.sh
> tez-dist/src/docker/am.env
> tez-dist/src/docker/build.sh
> ...
> and later
> ...
> tez-dist/src/docker/task-entrypoint.sh
> tez-dist/src/docker/task.env
> tez-dist/src/docker/entrypoint.sh <- this can be used in Dockerfile, and an env parameter from docker-compose can distinguish which final entrypoint script is called
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)