Actions
Bug #6998
closed[Docker] Workbench image doesn't serve HTTPS
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Docker
Target version:
-
Story points:
-
Description
Steps to reproduce:
$ docker pull arvados/workbench $ docker run --name=workbenchbug arvados/workbench $ curl --verbose -kLf "http://$(docker inspect workbenchbug | grep IPAddress | cut -d\" -f4)"
The last command is analogous to what arvdock
runs to detect when the cluster is ready. It doesn't work, because the response is a 301 to redirect the URL to HTTPS, but the Workbench Docker image has no configuration to serve HTTPS.
I think the simplest fix is to set force_ssl: false
in the image's application.yml
, but there may be other options.
Updated by Brett Smith over 8 years ago
- Subject changed from [Docker] Workbench image redirects to HTTPS, but doesn't serve HTTPS to [Docker] Workbench image doesn't serve HTTPS
- Target version changed from 2015-09-02 sprint to Arvados Future Sprints
I pushed the simple fix, which makes this less pressing. I'll leave this ticket open if we want to consider more thorough solutions like having the image serve HTTPS.
Updated by Tom Morris about 5 years ago
- Target version deleted (
Arvados Future Sprints)
Actions