Docker desktop SIGABRT error in containers log
Damba1974 opened this issue · comments
Hi everyone.
Im using docker desktop for a years and till now work perfect.
Now I get “SIGABRT” error and my docker does not work correctly. I tryed reinstall Docker but I get same problem.
How can I solve this error?
Here is logs of my container:
2024-03-22 21:15:21
2024-03-22 21:15:21 Starting Stellar Quickstart
2024-03-22 21:15:21
2024-03-22 21:15:21 mode: persistent
2024-03-22 21:15:21 network: testnet (Pi Testnet)
2024-03-22 21:15:21 postgres: config directory exists, skipping copy
2024-03-22 21:15:21 supervisor: config directory exists, skipping copy
2024-03-22 21:15:21 stellar-core: config directory exists, skipping copy
2024-03-22 21:15:21 horizon: config directory exists, skipping copy
2024-03-22 21:15:21 postgres: already initialized
2024-03-22 21:15:21 chown-core: ok
2024-03-22 21:15:21 core: already initialized
2024-03-22 21:15:21 horizon: already initialized
2024-03-22 21:15:21 starting supervisor
2024-03-22 21:15:22 2024-03-22 20:15:22,502 CRIT Supervisor running as root (no user in config file)
2024-03-22 21:15:22 2024-03-22 20:15:22,549 INFO RPC interface 'supervisor' initialized
2024-03-22 21:15:22 2024-03-22 20:15:22,550 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-03-22 21:15:22 2024-03-22 20:15:22,551 INFO supervisord started with pid 1
2024-03-22 21:15:23 2024-03-22 20:15:23,558 INFO spawned: 'postgresql' with pid 20
2024-03-22 21:15:23 2024-03-22 20:15:23,569 INFO spawned: 'stellar-core' with pid 21
2024-03-22 21:15:24 2024-03-22 20:15:24,799 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:15:24 2024-03-22 20:15:24,800 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:15:44 2024-03-22 20:15:44,910 INFO spawned: 'horizon' with pid 284
2024-03-22 21:15:46 2024-03-22 20:15:46,154 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:06 2024-03-22 20:16:06,444 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:07 2024-03-22 20:16:07,306 INFO spawned: 'stellar-core' with pid 579
2024-03-22 21:16:09 2024-03-22 20:16:09,221 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:16 2024-03-22 20:16:16,846 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:16 2024-03-22 20:16:16,900 INFO spawned: 'stellar-core' with pid 634
2024-03-22 21:16:18 2024-03-22 20:16:18,006 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:25 2024-03-22 20:16:25,976 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:26 2024-03-22 20:16:26,308 INFO spawned: 'stellar-core' with pid 688
2024-03-22 21:16:28 2024-03-22 20:16:28,257 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:35 2024-03-22 20:16:35,889 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:36 2024-03-22 20:16:36,306 INFO spawned: 'stellar-core' with pid 742
2024-03-22 21:16:38 2024-03-22 20:16:38,220 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:46 2024-03-22 20:16:46,023 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:46 2024-03-22 20:16:46,307 INFO spawned: 'stellar-core' with pid 803
2024-03-22 21:16:47 2024-03-22 20:16:47,528 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:16:55 2024-03-22 20:16:55,474 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:16:55 2024-03-22 20:16:55,491 INFO spawned: 'stellar-core' with pid 857
2024-03-22 21:16:57 2024-03-22 20:16:57,396 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:17:04 2024-03-22 20:17:04,511 INFO exited: stellar-core (terminated by SIGABRT; not expected)
2024-03-22 21:17:05 2024-03-22 20:17:05,309 INFO spawned: 'stellar-core' with pid 911
2024-03-22 21:17:06 2024-03-22 20:17:06,653 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-22 21:17:15 2024-03-22 20:17:15,431 INFO exited: stellar-core (terminated by SIGABRT; not expected)
...
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed.