[
https://issues.apache.org/jira/browse/RANGER-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-5009:
-----------------------------------
Component/s: docker
(was: admin)
(was: audit)
(was: build-infra)
(was: documentation)
(was: ger)
(was: intg)
(was: kms)
(was: plugins)
(was: Ranger)
(was: tagsync)
(was: usersync)
Fix Version/s: 3.0.0
(was: 2.7.0)
> `ranger_in_docker` only determines Docker Compose V1 and not Docker Compose V2
> ------------------------------------------------------------------------------
>
> Key: RANGER-5009
> URL: https://issues.apache.org/jira/browse/RANGER-5009
> Project: Ranger
> Issue Type: Bug
> Components: docker
> Reporter: Qiheng He
> Assignee: Chinmay N Hegde
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> - *ranger_in_docker* only determines Docker Compose V1 and not Docker Compose
> V2. See
> [https://github.com/apache/ranger/blob/release-ranger-2.5.0/ranger_in_docker#L136]
> .
> {code:none}
> docker-compose --version > /dev/null 2>&1
> if [ $? -ne 0 ]
> then
> echo "ERROR: You must have a valid DOCKER installed on your system to do
> a docker build. (error running docker-compose command)"
> exit 1
> fi
> {code}
>
> - This will prevent everyone from compiling Docker Images, because Docker
> Compose V2 has become a Docker Plugin, and the command is {*}docker
> compose{*}.
> - I honestly have no idea what module this actually corresponds to, the JIRA
> issue template requires me to set the module. I just checked the module I
> thought was problematic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
