Open alanking opened 1 week ago
I tried restarting the service and saw the server come up and run normally. It's only the initial attempt that fails, it seems.
and noting here, intiial and restarted both connect fine for me. so we're not yet sure how to trap this or what it means.
works for me:
$ docker compose up irods-client-s3-api
[+] Running 4/4
✔ Container irods-demo-minio-1 Created 0.1s
✔ Container irods-demo-irods-catalog-1 Created 0.1s
✔ Container irods-demo-irods-catalog-provider-1 Created 0.0s
✔ Container irods-demo-irods-client-s3-api-1 Created 0.0s
Attaching to irods-client-s3-api-1
irods-client-s3-api-1 | [2024-11-13 00:59:41.899] [P:1] [info] [T:1] Initializing server.
irods-client-s3-api-1 | [2024-11-13 00:59:42.192] [P:1] [info] [T:1] Server is ready.
Another update... I don't even have to restart the service myself. The restart
directive in the Compose file causes the service to come up successfully all by itself. I only know this because I run this to follow the output after docker compose up
returns my prompt:
docker compose logs -f irods-client-s3-api
So... in the end, the service is running, but it just fails the first time for some reason.
nothing more than ... because the irods provider wasn't yet ready?
the initial connection is required to standup the s3 api... but then.. i believe it will gracefully reconnect in case the provider 'goes away' and comes back...
Using tip of main, I get the following output:
I tried updating to 0.3.0...
...and got a bit more: