SIGABRT error in containers log

Docker Desktop for Windows
1

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)
...
2

This appears to be a problem with the application inside the image itself.
Please raise an issue in the Github project of this application: Issues · stellar/quickstart · GitHub

3

Thank you meyay.
Best regards

4

The image is old, it has not been changed for more than a year and was working normally until a few days ago and now it has a SIGBART error. What do you think could be the cause of this error?
Thank you

5

How is the image old, if it’s build 17 days ago?

Even if the Dockerfile and none of the sources and scripts changed for a year, the packages of the os inside the image, and the dependencies won’t be identical, would they?

Another thing that comes to mind is that Docker Desktop might use newer kernel versions in their utility vm, which might cause problems with kernel calls.

The world constantly evolves and dependencies that worked flawless today, might break at one point.

1 Like
6

The image was built more than a year ago. Thanks for your explanation of the details I hadn’t thought of on my own.

7

Which tag of the image? Because the latest tag is just 2,5 weeks old

image
image1018×892 48 KB

8

Unfortunately, this is a misunderstanding because a colleague opened a problem related to the following image:
pinetwork/pi-node-docker: latest

ned, 24. ožu 2024. u 18:41 Metin Y. via Docker Community Forums <notifications@docker.discoursemail.com> napisao je:

9

This topic is about SIGABRT with the image from the stellar/quickstart repo.

If you use another repo, please create your own topic and add as much information as possible that helps someone, who doesn’t know your context, to understand what you are writing about.