Selvamohan Neethiraj created RANGER-5559:
--------------------------------------------

             Summary: anger Docker: Startup failures due to insufficient 
filesystem permissions on execution of chown command & moving files into 
/usr/bin
                 Key: RANGER-5559
                 URL: https://issues.apache.org/jira/browse/RANGER-5559
             Project: Ranger
          Issue Type: Improvement
          Components: docker
    Affects Versions: 2.8.0
            Reporter: Selvamohan Neethiraj
            Assignee: Selvamohan Neethiraj


Error messages during startup:
{code:java}
2026-04-17 14:13:46,474  [I] Creating 
/opt/ranger/admin/ews/webapp/WEB-INF/classes/lib
2026-04-17 14:13:46,525  [I] Setting up init.d
cp: cannot create regular file '/etc/init.d/ranger-admin': Permission denied
chmod: cannot access '/etc/init.d/ranger-admin': No such file or directory
2026-04-17 14:13:46,635  [I] Creating script S88ranger-admin/K90ranger-admin in 
/etc/rc2.d directory .... 
ln: failed to create symbolic link '/etc/rc2.d/S88ranger-admin': Permission 
denied
ln: failed to create symbolic link '/etc/rc2.d/K90ranger-admin': Permission 
denied
2026-04-17 14:13:46,841  [I] Creating script S88ranger-admin/K90ranger-admin in 
/etc/rc3.d directory .... 
ln: failed to create symbolic link '/etc/rc3.d/S88ranger-admin': Permission 
denied
ln: failed to create symbolic link '/etc/rc3.d/K90ranger-admin': Permission 
denied
2026-04-17 14:13:46,890  [I] RANGER ADMIN LOGBACK CONF FILE : 
/opt/ranger/admin/ews/webapp/WEB-INF/classes/conf/logback.xml
2026-04-17 14:13:47,049  [I] Setting up installation files and directory DONE
chown: changing ownership of '/opt/ranger/admin': Operation not permitted{code}
Also, while creation of ranger-services during startup, it assumes the hostname 
of the ranger-service is "ranger" whereas it would be different in-case of a 
k8s environment. This causes HTTP failure.  Also, we need a flag to prevent 
auto-creation of these sample ranger-services in the ranger-admin (for 
production deployment!)



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

Reply via email to