[
https://issues.apache.org/jira/browse/RANGER-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4500:
-----------------------------------
Description:
Currently, docker-compose for a service specifies the dependencies required for
a service when the service comes up in a container. This happens via the
`depends_on` flag to control the sequence of service start up. However, this
leads to docker-compose requiring the same dependencies to be built as image
while building the original docker image with docker-compose build command.
For ex: ranger-admin image needs no change when ranger-tagsync image needs to
be rebuilt but current setup requires ranger-admin image to be rebuilt as well
when building ranger-tagsync image.(with docker-compose build)
Using external_links in docker_compose may be a possible approach here.
CC: [~madhan]
was:
Currently, docker-compose for a service specifies the dependencies required for
a service when the service comes up in a container. This happens via the
`depends_on` flag to control the sequence of service start up. However, this
leads to docker-compose requiring the same dependencies to be built as image
while building the original docker image with docker-compose build command.
For ex: ranger-admin image needs no change when ranger-tagsync image needs to
be rebuilt but current setup requires ranger-admin image to be rebuilt as
well.(with docker-compose build)
Using external_links in docker_compose may be a possible approach here.
CC: [~madhan]
> Build docker images independently with docker-compose
> -----------------------------------------------------
>
> Key: RANGER-4500
> URL: https://issues.apache.org/jira/browse/RANGER-4500
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Abhishek Kumar
> Priority: Major
>
> Currently, docker-compose for a service specifies the dependencies required
> for a service when the service comes up in a container. This happens via the
> `depends_on` flag to control the sequence of service start up. However, this
> leads to docker-compose requiring the same dependencies to be built as image
> while building the original docker image with docker-compose build command.
> For ex: ranger-admin image needs no change when ranger-tagsync image needs to
> be rebuilt but current setup requires ranger-admin image to be rebuilt as
> well when building ranger-tagsync image.(with docker-compose build)
> Using external_links in docker_compose may be a possible approach here.
> CC: [~madhan]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
