[hopefully fixed!] ca-load container fails to start

[yzhong32]

After cloning the Distro repository, I attempted to use the command docker-compose -f develop.yml up to build and run the containers. However, I faced a consistent issue where the ca-load container failed to start, exiting with an error message. Has anyone else faced the same issue and knows how to solve it?

[gbengaoluwadahunsi]

Hello @yzhong32 ,
same here like many others, we are trying to fix that, we might have to call the attention of @birm to guide us through.

[birm]

Can someone test if a recent change that I've done fixes this for you by running the build command again? This has been a lot more trouble than expected!

[We13b-MD]

i will test it soon working on it

[gbengaoluwadahunsi]

Ok Birm

…

On Sun, Mar 10, 2024, 5:02 PM Birm ***@***.***> wrote: Can someone test if a recent change that I've done fixes this for you by running the build command again? This has been a lot more trouble than expected! — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASMPOGKEMLE4D3U3EI4PVODYXQOQXAVCNFSM6AAAAABEOVRKD6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DOMZUGQ2TE> . You are receiving this because you commented.Message ID: ***@***.*** com>

[gbengaoluwadahunsi]

Hello @birm,
I forked, cloned, and ran the Distro app again and still having the same error, the ca-loader is giving an error after uploadding the image.

[birm]

Can you please run docker-compose -f develop.yml build loader --no-cache then restart it in hopes it helps?

[yzhong32]

Can you please run docker-compose -f develop.yml build loader --no-cache then restart it in hopes it helps?

Hello Birm , after executing the rebuild and restart commands, the ca-load container is now operational.

[gbengaoluwadahunsi]

Hello @birm, ca loader is working perfectly now
Thanks