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 vote343 views1 answer
The token has been blacklisted laravel jwt
PHP Laravel
4 votes271 views1 answer
Convert a value to a float in php
PHP
0 vote259 views1 answer
Laravel model isdirty
PHP
0 vote296 views1 answer
Send OTP php
PHP
6 votes361 views2 answers
Installing livewire on laravel v6
PHP Laravel
5 votes311 views4 answers
Laravel collection merge
PHP Laravel
1 vote294 views1 answer
Get contents of a tmp file php
PHP
0 vote290 views1 answer
Mysql Cannot pass parameter 2 by reference
PHP
0 vote285 views1 answer
Remove default product data tabs
PHP
14 votes324 views3 answers
Change returning datetime timezone to recalculate with user timezone laravel
PHP Laravel