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

20 votes187 views5 answers
Php artisan cache all
PHP
0 vote130 views1 answer
Encryption key has not encrypted laravel
PHP
0 vote140 views1 answer
Laravel adding new items to config run time
PHP Laravel
12 votes119 views2 answers
Php how to delete file
PHP
0 vote115 views1 answer
Twig to pdf
PHP
0 vote151 views1 answer
Laravel ID Generator
PHP Laravel
1 vote120 views1 answer
Php force image refresh
PHP
0 vote118 views1 answer
Ent_quotes in php
PHP
0 vote120 views2 answers
Php create 404 error
PHP
1 vote206 views1 answer
Check email exist or not wordpress
PHP