Project

General

Profile

Actions

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

Added by Robert Syme about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
Start date:
11/04/2014
Due date:
% Done:

0%

Estimated time:
Story points:
-

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.

Actions

Also available in: Atom PDF