Bug #4406
closed
[Docker] Default arvdock doesn't start sso server container, but also assumes that it exists by linking it to the API container
0%
Description
Hi all. I hope this is helpful. My apologies in advance if I'm doing something wrong.
A naive user would usualy attempt to start the docker images using
$ ./arvdock start # From the docker directory.
This simple usage doesn't start the sso container (ine 237 commented out).
Line 253 initates the API server startup and requests a link to the non-existant sso server with '--link sso_server:sso'.
I think this could be fixed up by:
if $start_api != false
then
if $start_sso != false
then
start_container "$start_api:443" "api_server" '' "sso_server:sso" "arvados/api"
else
start_container "$start_api:443" "api_server" '' '' "arvados/api"
fi
fi
I like what you guys are heading with Arvados. I'll try and help out where I can.
Updated by Brett Smith about 10 years ago
- Subject changed from Default arvdock doesn't start sso server container, but also assumes that it exists by linking it to the API container to [Docker] Default arvdock doesn't start sso server container, but also assumes that it exists by linking it to the API container
- Target version set to Bug Triage
Updated by Ward Vandewege about 10 years ago
- Status changed from New to Resolved
- Target version changed from Bug Triage to 2014-11-19 sprint
This was already fixed in commits a6606b79fb6496e43eef6b2e8b04d5c1061f5635 and 3978e8ae9c1b5bbc07c63fd062e189a81e52399c, earlier this week.
A git pull is probably in order!
Thanks,
Ward.