You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While installing liferay portal 7.4.3.19 on openshift in ibm cloud facing the below error message, has anyone faced the below issues on ibm cloud?
[LIFERAY] To SSH into this container, run: "docker exec -it liferay-867858448b-vw8pb /bin/bash".
[LIFERAY] Using zulu8 JDK. You can use another JDK by setting the "JAVA_VERSION" environment varible.
[LIFERAY] Run this container with the option "-v $(pwd)/xyz123:/mnt/liferay" to bridge $(pwd)/xyz123 in the host operating system to /mnt/liferay on the container.
[LIFERAY] The directory /mnt/liferay/files does not exist. Create the directory $(pwd)/xyz123/files on the host operating system to create the directory /mnt/liferay/files on the container. Files in /mnt/liferay/files will be copied to /opt/liferay before Liferay Portal starts.
[LIFERAY] The directory /mnt/liferay/scripts does not exist. Create the directory $(pwd)/xyz123/scripts on the host operating system to create the directory /mnt/liferay/scripts on the container. Files in /mnt/liferay/scripts will be executed, in alphabetical order, before Liferay Portal starts.
[LIFERAY] The directory /mnt/liferay/deploy does not exist. Create the directory $(pwd)/xyz123/deploy on the host operating system to create the directory /mnt/liferay/deploy on the container. Copy files to $(pwd)/xyz123/deploy to deploy modules to Liferay Portal at runtime.
/usr/local/bin/liferay_entrypoint.sh: line 39: /opt/liferay/liferay.pid: Permission denied
[LIFERAY] Starting Liferay Portal. To stop the container with CTRL-C, run this container with the option "-it".
/usr/local/bin/start_liferay.sh: line 19: /opt/liferay/tomcat/bin/catalina.sh: Permission denied
/usr/local/bin/start_liferay.sh: line 19: exec: /opt/liferay/tomcat/bin/catalina.sh: cannot execute: Permission denied
getting this error while creating deployment config from the container image.
ERRO[0442] error waiting for container: unexpected EOF --> this error while running docker run -it -v $(pwd)/usr/liferay:/etc/liferay/mount --name liferay-dxp -p 80:8080 liferay/portal:7.4.3.19-ga19
The text was updated successfully, but these errors were encountered:
While installing liferay portal 7.4.3.19 on openshift in ibm cloud facing the below error message, has anyone faced the below issues on ibm cloud?
[LIFERAY] Using zulu8 JDK. You can use another JDK by setting the "JAVA_VERSION" environment varible.
[LIFERAY] Run this container with the option "-v$(pwd)/xyz123:/mnt/liferay" to bridge $ (pwd)/xyz123 in the host operating system to /mnt/liferay on the container.
[LIFERAY] The directory /mnt/liferay/files does not exist. Create the directory $(pwd)/xyz123/files on the host operating system to create the directory /mnt/liferay/files on the container. Files in /mnt/liferay/files will be copied to /opt/liferay before Liferay Portal starts.
[LIFERAY] The directory /mnt/liferay/scripts does not exist. Create the directory $(pwd)/xyz123/scripts on the host operating system to create the directory /mnt/liferay/scripts on the container. Files in /mnt/liferay/scripts will be executed, in alphabetical order, before Liferay Portal starts.
[LIFERAY] The directory /mnt/liferay/deploy does not exist. Create the directory$(pwd)/xyz123/deploy on the host operating system to create the directory /mnt/liferay/deploy on the container. Copy files to $ (pwd)/xyz123/deploy to deploy modules to Liferay Portal at runtime.
/usr/local/bin/liferay_entrypoint.sh: line 39: /opt/liferay/liferay.pid: Permission denied
[LIFERAY] Starting Liferay Portal. To stop the container with CTRL-C, run this container with the option "-it".
/usr/local/bin/start_liferay.sh: line 19: /opt/liferay/tomcat/bin/catalina.sh: Permission denied
/usr/local/bin/start_liferay.sh: line 19: exec: /opt/liferay/tomcat/bin/catalina.sh: cannot execute: Permission denied
getting this error while creating deployment config from the container image.
The text was updated successfully, but these errors were encountered: