Composer: file_put_contents(./composer.json): failed to open stream: Permission denied

I had this problem to install laravel/lumen.

It can be resolved with the following command:

$ sudo chown -R $USER ~/.composer/

---

To resolve this, you should open up a terminal window and type this command:

sudo chown -R user ~/.composer (with user being your current user, in your case, kramer65)

After you have ran this command, you should have permission to run your composer global require command.

You may also need to remove the .composer file from the current directory, to do this open up a terminal window and type this command:

sudo rm -rf .composer

---

For me, in Ubuntu 18.04. I needed to chown inside ~/.config/composer/

E.g.

sudo chown -R $USER ~/.config/composer

Then global commands work.

---

In my case I don't have issues with ~/.composer.
So being inside Laravel app root folder, I did sudo chown -R $USER composer.lock and it was helpful.

---

In my case, .composer was owned by root, so I did sudo rm -fr .composer and then my global require worked.

Be warned! You don't wanna use that command if you are not sure what you are doing.

---

I faced this issue as well but in my case, I was in wrong directory. Check the directory you are working

---

In my case all the permissions were correct at all the locations manetioned in other answers here, but I was still getting this error.

Turned out there were some vendor directories that were owned by root. Composer writes composer.lock files all over the place when it's doing an update or install.

So solving my case - and this is specifically for a laravel sail container - all ownerships were switched to user sail in the project:

Enter the sail container as root:

vendor/bin/sail root-shell

Set the file ownership for all files in the project:

chown -R sail:sail /var/www/html

You may just want to do the vendor directory only as a first try:

chown -R sail:sail /var/www/html/vendor

The ownership was wrong after switching from a hand-rolled docker-compose.yaml setup to Laravel Sail, which IMO handles file ownership and permissions in a sensible way, separating root from the application user sail.

---

This might be super edge case, but if you are using Travis CI and taking advantage of caching, you might want to clear all cache and retry.

Fixed my issue when I was going from sudo to non sudo builds.

---

I was getting the same exception, but in my case I am using PowerShell to run commands So, I fixed this with an instruction to unblock multiple files first. PS C:\> dir C:\executable_file_Path\*PowerShell* | Unblock-File and then use the following to load the package & 'C:\path_to_executable\php.exe' "c:\path_to_composer_.phar_file\composer.phar "require desired/package

---

In my case I used sudo mkdir projectFolder to create folder. It was owned by root user and I was logged in using non root user.

So I changed the folder permission using command sudo chown mynonrootuser:mynonrootuser projectFolder and then it worked fine.

---

I was getting the same error when using it with WSL Windows 10. I used the following command to solve it:-

sudo chown -R $USER  /home/<username>/.config/composer

---

I had same issue in windows version of composer that has installed in

C:\composer

When I was trying this command

C:\composer require aws/aws-sdk-php

then simply I got into composer installed folder and try it again

C:\composer>composer require aws/aws-sdk-php

the package installed quickly .

---