docker-magento: Missing write permissions

So I reinstalled everything from repo.

When I do ./bin/setup I get the following errors

                                                     
  [Exception]                                        
  Missing write permissions to the following paths:  
  /var/www/html/var/composer_home/composer.lock      
  /var/www/html/var/composer_home/cache              
  /var/www/html/var/composer_home/vendor             
  /var/www/html/var/composer_home/.htaccess     

and many of these

chmod: changing permissions of 'var/composer_home/vendor/symfony/polyfill-mbstring/Mbstring.php': Operation not permitted
chmod: changing permissions of 'var/composer_home/vendor/symfony/polyfill-mbstring/bootstrap.php': Operation not permitted
chmod: changing permissions of 'var/composer_home/vendor/symfony/polyfill-mbstring/README.md': Operation not permitted

and this


  [Symfony\Component\Console\Exception\CommandNotFoundException]  
  There are no commands defined in the "deploy:mode" namespace.   
                                                                                                                                    
  [Symfony\Component\Console\Exception\CommandNotFoundException]  
  There are no commands defined in the "indexer" namespace.       

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

ok, i ditched docker-sync. there is a much better way. the permissions have completely changed and are now set in the dockerfiles, this should take care of absolutely everything related to ownerships and permissions. they are building right now on dockerhub, please wait for the new images to complete building and you can retest. note the new readme, there is a very different docker-compose.yml file now and way of configuring. it’s much simpler now. i’ll close this out, but feel free to update here and/or reopen if you are still having problems. hope you like the new images 😃

Thank you. I’m going to reopen this ticket and leave it open until I investigate since a possible fix for a possible problem is here.