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
What is the expected result of these steps in the absence of the issue?
It should start the app
What is the actual result?
Some files inside container inherit permissions from source host, which means they aren't readable inside container.
First example (from possibly more) -
$ docker run -ti spryker_b2b_base_cli:1.0
$ ls -la /usr/local/etc/php/php.ini
-rw-r----- 1 root root 70953 Feb 18 16:34 php.ini
What possible solutions and/or workarounds for the issue do you see?
Permissions of files inside container should be controlled by build process and not rely on operating system's umask, which can be different (espacially on CI systems)
Is there any other information that might be helpful?
The text was updated successfully, but these errors were encountered:
Which release, branch or hash of Docker SDK are you using?
1.30.0
Which operating system (platform/version/architecture) are you using?
Linux Debian
What is the issue that you're experiencing?
docker/sdk
fails in several places, whenumask != 022
What are the steps to reproduce the issue?
What is the expected result of these steps in the absence of the issue?
It should start the app
What is the actual result?
Some files inside container inherit permissions from source host, which means they aren't readable inside container.
First example (from possibly more) -
What possible solutions and/or workarounds for the issue do you see?
Permissions of files inside container should be controlled by build process and not rely on operating system's umask, which can be different (espacially on CI systems)
Is there any other information that might be helpful?
The text was updated successfully, but these errors were encountered: