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

7 votes330 views2 answers
Last recode of DB using laravel
PHP Laravel
0 vote366 views1 answer
Uncaught jquery-numerator requires jQuery to be loaded first wordpress
PHP Wordpress
0 vote349 views1 answer
Laravel Deployment to google cloud app engine flexible environment app.yaml file
PHP
0 vote317 views1 answer
Php get first digit of number
PHP
0 vote330 views2 answers
Laravel pdf export
PHP
1 vote392 views2 answers
Pass image path in laravel blade
PHP Laravel
3 votes379 views3 answers
Laravel if database has table
PHP Laravel
0 vote319 views1 answer
Get slogan wp
PHP
0 vote324 views1 answer
Getting key from env returns null laravel
PHP
0 vote323 views1 answer
Laravel controller constructor auth user null
PHP