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

0 vote274 views1 answer
Laravel add package without updating
PHP Laravel
1 vote230 views1 answer
Laravel bindings query
PHP Laravel
1 vote214 views1 answer
$_server 'remote_addr' not working properly
PHP
1 vote211 views2 answers
Db name laravel
PHP
7 votes208 views3 answers
Php merge array with same value
PHP
2 votes194 views2 answers
Jquery click function not working
PHP
0 vote217 views1 answer
Tinyinteger laravel +size
PHP
0 vote214 views2 answers
Php variables examples
PHP
0 vote193 views3 answers
Grepper answers
PHP
1 vote218 views1 answer
Check if session variable exists php
PHP