-
Notifications
You must be signed in to change notification settings - Fork 346
Implement ACL support in PermissionsHandler #1127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Added ACL support check and fallback to traditional permissions. Improved error handling for permission setting. On Warden docker error : > Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions Script Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions handling the set-permissions event terminated with an exception The following exception is caused by a process timeout Check https://getcomposer.org/doc/06-config.md#process-timeout for details In Process.php line 1205: The process "setfacl -Rm "u:`whoami`:rwX,d:u:`whoami`:rwX,g:`whoami`:rw,d:g:`whoami`:rw" var/cache" exceeded the timeout of 60 seconds.
|
@Genaker Can you clarify what you mean by "Warden docker"? AFAIK, Warden does not yet support a compatible environment – https://docs.warden.dev/environments/types.html
RPM-based distributions such as RHEL, Oracle Linux, CentOS, and Fedora would align most closely with the production-proven environments used in OroCloud. Ubuntu, Debian, and Arch are also widely used by OroCommerce developers and fully support It may not be available on Alpine by default, and past experience shows that Alpine can introduce additional issues when running OroCommerce, so we cannot recommend it anyway. |
|
It is on Centos 9 Docker when /var/www/html attached to the Windows host machine |
|
@Genaker Please run the following command from inside the container and share the output: stat -f -c '%T' /var/www/htmlMy guess is that your volumes:
- "C:/Users/someuser/orocommerce:/var/www/html"In this setup, the source path is on NTFS and is exposed into the Linux container via Docker Desktop's file-sharing layer (9p / drvfs / virtiofs, depending on the configuration). In this case, POSIX ACLs are not available, so I am still not sure we should allow running the installation without
These problems can be avoided by keeping the project on a Linux filesystem and mounting it from there:
Projects stored inside WSL remain fully accessible from the Windows host even when containers are not running - Windows will automatically start WSL on access. The main thing to avoid though is unregistering the WSL distribution (for example via |
|
Just a note for myself:
|
|
Hi Michael,
The environment being used is WSL2, which currently lacks ACL tools. Even
when the project root folder is not a complete bind mount, ACL issues
persist when some folders ore files are mounted to the host windows WSL2
due to the lack of native support.
I am aware that Oro does not officially support Windows development
environments. However, the proposed solution functions effectively as a
fallback and resolves the current operational issues.
Thanks,
Yegor Shytikov
…On Fri, Dec 12, 2025 at 10:27 AM Michael Bessolov ***@***.***> wrote:
*mbessolov* left a comment (oroinc/platform#1127)
<#1127 (comment)>
Just a note for myself:
- PowerShell: wsl --list --verbose
- PowerShell: wsl --set-version CentOS-Stream-9 2
- Docker Desktop > Settings > General: enable Use the WSL 2 based
engine
- Docker Desktop > Settings > Resources > WSL Integration: enable for
CentOS
- WSL shell: docker info
- WSL shell: docker context ls
—
Reply to this email directly, view it on GitHub
<#1127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGJNZQHUDBHQUPJ47OQVET4BMCHVAVCNFSM6AAAAACOZJTTCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBXGY2DMNZXGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
It is not Centos 9 issue. But Mount issue to Windows host system:
microsoft/WSL#2750
…On Fri, Dec 12, 2025 at 10:27 AM Michael Bessolov ***@***.***> wrote:
*mbessolov* left a comment (oroinc/platform#1127)
<#1127 (comment)>
Just a note for myself:
- PowerShell: wsl --list --verbose
- PowerShell: wsl --set-version CentOS-Stream-9 2
- Docker Desktop > Settings > General: enable Use the WSL 2 based
engine
- Docker Desktop > Settings > Resources > WSL Integration: enable for
CentOS
- WSL shell: docker info
- WSL shell: docker context ls
—
Reply to this email directly, view it on GitHub
<#1127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGJNZQHUDBHQUPJ47OQVET4BMCHVAVCNFSM6AAAAACOZJTTCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBXGY2DMNZXGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think that applies to NTFS filesystem exposed to WSL: It will be avoided when:
The Windows will create a VHDX virtual disk, formatted as ext4 inside that VHDX, and made it available to the WSL Linux distro. That will be a true fully initialized Linux filesystem. |
Added ACL support check and fallback to traditional permissions. Improved error handling for permission setting.
On Warden docker environment command "composer install" error : > Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions Script Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions handling the set-permissions event terminated with an exception The following exception is caused by a process timeout Check https://getcomposer.org/doc/06-config.md#process-timeout for details
In Process.php line 1205:
The process "setfacl -Rm "u:
whoami:rwX,d:u:whoami:rwX,g:whoami:rw,d:g:whoami:rw" var/cache" exceeded the timeout of 60 seconds.full log: