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
{{ message }}
This repository was archived by the owner on Mar 29, 2023. It is now read-only.
The idea of 2 Dockerfile is being used because in Linux the files created inside the Docker container are owned by root. So the normal user will face permission issue on the PDF and log files. However, in Mac, no such problem is encountered and the files are owned by the logged in user.
In Linux we need to create a user in the container with the same permissions as of logged in user. This allows the files to be owned by that user. This step forced us to create a separate Dockerfile which is platform dependent. The automation script detects the platform and proceeds with the correct Dockerfile accordingly.
However, this is not an ideal case solution. We would like to have only 1 Dockerfile. Any new approach to resolve this issue is welcome!
Currently MARS uses separate Dockerfile for Linux and Mac. They can be found here:
The idea of 2 Dockerfile is being used because in Linux the files created inside the Docker container are owned by root. So the normal user will face permission issue on the PDF and log files. However, in Mac, no such problem is encountered and the files are owned by the logged in user.
In Linux we need to create a user in the container with the same permissions as of logged in user. This allows the files to be owned by that user. This step forced us to create a separate Dockerfile which is platform dependent. The automation script detects the platform and proceeds with the correct Dockerfile accordingly.
However, this is not an ideal case solution. We would like to have only 1 Dockerfile. Any new approach to resolve this issue is welcome!