Cpanel composer update kill

The "Killed" message usually means your process consumed too much memory, so you may simply need to add more memory to your system if possible. At the time of writing this answer, I've had to increase my virtual machine's memory to at least 768MB in order to get composer update to work in some situations.

However, if you're doing this on a live server, you shouldn't be using composer update at all. What you should instead do is:

Run composer update in a local environment (such as directly on your physical laptop/desktop, or a docker container/VM running on your laptop/desktop) where memory limitations shouldn't be as severe.
Upload or git push the composer.lock file.
Run composer install on the live server.
composer install will then read from the .lock file, fetching the exact same versions every time rather than finding the latest versions of every package. This makes your app less likely to break, and composer uses less memory.

Source: stackoverflow.com

Similar codes

1 vote132 views1 answer
Increment single column laravel
PHP Laravel
2 votes101 views3 answers
Where is in array laravel
PHP
2 votes120 views2 answers
Truncate table laravel eloquent
PHP
1 vote138 views1 answer
Laravel multiple group by
PHP Laravel
0 vote136 views1 answer
Update Query in Codeigniter Using Multiple Where Condition
PHP CodeIgniter
1 vote101 views1 answer
Fixuphost
PHP
4 votes109 views1 answer
Types of method in api
PHP
9 votes126 views5 answers
Laravel updateOrInsert
PHP Laravel
0 vote142 views1 answer
Redirect to intent url after login laravel
PHP Laravel
0 vote106 views1 answer
Uncaught jquery-numerator requires jQuery to be loaded first wordpress
PHP