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

Wei-Chiu Chuang updated HDDS-12631:
-----------------------------------
    Description: 
I thought HDDS-11915 fixed it but it didn't, and when running tests on a Mac 
M3, SCM won't start for the same "libcrypt.so.1: cannot open shared object 
file: No such file or directory" error.

The problem is that LD_LIBRARY_PATH in Dockerfile isn't pointing to the right 
path. libcrypt.so.1 is installed at /lib64/ and /usr/lib64 so it should point 
to there accordingly.

 

After fixing ozone-runner Docker image, the ozone docker image must also be 
regenerated otherwise upgrade test won't start either. 
[https://github.com/apache/ozone-docker/]

  was:
I thought HDDS-11915 fixed it but it didn't, and when running tests, SCM won't 
start for the same "libcrypt.so.1: cannot open shared object file: No such file 
or directory" error.

The problem is that LD_LIBRARY_PATH in Dockerfile isn't pointing to the right 
path. libcrypt.so.1 is installed at /lib64/ and /usr/lib64 so it should point 
to there accordingly.

 

After fixing ozone-runner Docker image, the ozone docker image must also be 
regenerated otherwise upgrade test won't start either. 
https://github.com/apache/ozone-docker/


> Correct LD_LIBRARY_PATH for ozone-runner Docker image
> -----------------------------------------------------
>
>                 Key: HDDS-12631
>                 URL: https://issues.apache.org/jira/browse/HDDS-12631
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>
> I thought HDDS-11915 fixed it but it didn't, and when running tests on a Mac 
> M3, SCM won't start for the same "libcrypt.so.1: cannot open shared object 
> file: No such file or directory" error.
> The problem is that LD_LIBRARY_PATH in Dockerfile isn't pointing to the right 
> path. libcrypt.so.1 is installed at /lib64/ and /usr/lib64 so it should point 
> to there accordingly.
>  
> After fixing ozone-runner Docker image, the ozone docker image must also be 
> regenerated otherwise upgrade test won't start either. 
> [https://github.com/apache/ozone-docker/]



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to