Magento Question posted in
The official documentation can be found here.

I can't delete the folder generated/code in Magento 2.2.6

I use Docker for my project. After installing the 2.2.6 package with sample data, it gives me problems like the following when I execute php bin/magento cache:clean

The file “/var/www/html/src/generated/code/Magento/Backend/App/Request/PathInfoProcessor/Proxy.php” cannot be deleted Warning!unlink(/var/www/html/src/generated/code/Magento/Backend/App/Request/PathInfoProcessor/Proxy.php):
No such file or directory

The generated/code folder can not be deleted and I have to restart my computer then it does let me delete the folder

I use php 7.1.22 , percona 5.6.39 and docker Version 18.06.1-ce-win73 (19507)

Tags:

4

Answers


  1. Chosen as BEST ANSWER
    0

    Installing magento 2 from the command line of the container in Docker solves the problem of writing permissions in Windows for me

    You may need to adjust the parameters:

    bin/magento setup:install --base-url=http://local.shop.magento2.com 
--db-host=db_magento2 --db-name=magento --db-user=magento --db-password=magento 
--admin-firstname=magento --admin-lastname=magento [email protected] 
--admin-user=admin --admin-password=admin123 --language=en_US 
--currency=USD --timezone=Europe/Madrid --use-rewrites=1

  2. 0

    This happens due to insufficient permissions on the project folder and files.Also www-data must be owner of the project if using Apache as web-server.
    Please execute commands given below:–

    • sudo chown -R www-data:www-data [path to magento directory]
    • navigate to root of your magento project
    • find . -type f -exec chmod 644 {} ;
    • find . -type d -exec chmod 755 {} ;
    • find ./var -type d -exec chmod 777 {} ;
    • find ./pub/media -type d -exec chmod 777 {} ;
    • find ./pub/static -type d -exec chmod 777 {} ;
    • chmod 777 ./app/etc
    • chmod 644 ./app/etc/*.xml
    • chmod u+x bin/magento
    Login or Signup to reply.
  3. 0

    Just in case anyone stumbles upon this:
    Add the following to your docker file

    RUN echo "root:root" | chpasswd

    This will allow you to switch to root and run chown

    su root
password:root
chown -R user:group /folder
    Login or Signup to reply.
  4. 0

    An important mania for people who offer their help is to think that all systems are the same.

    www-data is the user as long as there are conditions, which many will not meet, because they prefer to use nginx + php-fpm instead of the generalist model.

    Other times, included in that model is not the user running Appache, nginx or in the end, php, is www-data.

    So the most correct answer is not:

    • Change the owner of the entire magento folder to www-data
    • Neither give permissions 777, this is the most common of all the aberrations in the network.

    Lo mas correcto sería

    1. Who executes the process you write in the magento directory?
    2. PHP writes as user or globally?
    3. I have consulted the configuration of my php (php, php-fpm, etc.) to verify which user is the one that executes the operations?

    Once we have that data then if we can execute

    sudo chown -R <user_correct>: <group_correct>

    And please, stop paying attention to those who always write chmod -R 777

    Or one day they will wake up without their site in a normal way but full of infections that are hardly curable.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search