[
https://issues.apache.org/jira/browse/RANGER-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065452#comment-18065452
]
Abhishek Kumar commented on RANGER-5514:
----------------------------------------
Ok, It is currently assumed when running the docker image that the network name
is 'rangernw' so using it outside this network may cause issues?
> Ranger Admin expects hostname ranger-admin.rangernw
> ---------------------------------------------------
>
> Key: RANGER-5514
> URL: https://issues.apache.org/jira/browse/RANGER-5514
> Project: Ranger
> Issue Type: Bug
> Components: docker
> Affects Versions: 2.8.0
> Reporter: Attila Doroszlai
> Priority: Major
>
> Ranger Admin docker image can only be used if hostname is set to
> {{ranger-admin.rangernw}}, otherwise we get the following errors:
> {code}
> An exception occured: HTTPConnectionPool(host='ranger-admin.rangernw',
> port=6080): Max retries exceeded with url:
> /service/public/v2/api/service/name/dev_hdfs (Caused by
> NameResolutionError("HTTPConnection(host='ranger-admin.rangernw', port=6080):
> Failed to resolve 'ranger-admin.rangernw' ([Errno -2] Name or service not
> known)"))
> An exception occured: HTTPConnectionPool(host='ranger-admin.rangernw',
> port=6080): Max retries exceeded with url:
> /service/public/v2/api/service/name/dev_yarn (Caused by
> NameResolutionError("HTTPConnection(host='ranger-admin.rangernw', port=6080):
> Failed to resolve 'ranger-admin.rangernw' ([Errno -2] Name or service not
> known)"))
> ...
> {code}
> There should be no such restriction, Ranger Admin contaner should use
> {{localhost}} to access itself during setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
