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
When you enter the container by typing docker-compose exec --user=laradock workspace bash, you start getting a bunch of permission issues with laradock user ( you can't use composer with root , that's ok) trying to run composer create-project laravel/laravel .
You're supposed to change www folder ownership to laradock with chown otherwise it won't even start installing,
Only then , you can run composer create-project laravel/laravel . and it runs smooth.
The command composer require crocodicstudio/crudbooster also raises a long list of compatibility issues that it's not able to fix by itself
Installation failed, reverting ./composer.json to its original content.
If you run composer diagnose you are tempted to run auto-healing commands like composer self-update but, again, laradock user is not allowed to.
Exit the container, enter as root, run composer self-update ,exit and enter again as laradock but again, this won't fix the issue.
Can you please help us identifying the missing / execeding requirement/s in composer.json?
Also running composer require with --ignore-platform-reqs won't fix the issue.
Thank you for this astonishing project, i'm trying a porting from a WAMP to a Linux containerized solution
The text was updated successfully, but these errors were encountered:
When you enter the container by typing docker-compose exec --user=laradock workspace bash, you start getting a bunch of permission issues with laradock user ( you can't use composer with root , that's ok) trying to run composer create-project laravel/laravel .
You're supposed to change www folder ownership to laradock with chown otherwise it won't even start installing,
Only then , you can run composer create-project laravel/laravel . and it runs smooth.
The command composer require crocodicstudio/crudbooster also raises a long list of compatibility issues that it's not able to fix by itself
Installation failed, reverting ./composer.json to its original content.
If you run composer diagnose you are tempted to run auto-healing commands like composer self-update but, again, laradock user is not allowed to.
Exit the container, enter as root, run composer self-update ,exit and enter again as laradock but again, this won't fix the issue.
Can you please help us identifying the missing / execeding requirement/s in composer.json?
Also running composer require with --ignore-platform-reqs won't fix the issue.
Thank you for this astonishing project, i'm trying a porting from a WAMP to a Linux containerized solution
The text was updated successfully, but these errors were encountered: