Alternate port setup for Docker

59 views
Skip to first unread message

Tom Scott

unread,
Nov 12, 2019, 10:22:35 PM11/12/19
to Opencast Users
Hello,

I'm having a bit of trouble getting Opencast (allinone v7.4) to run in a docker container and expose an alternate port (18080:8080), everything is fine except for the player port which is trying to access media on port 8080 and failing (as it's only accessible through 18080).

I've tried environment variable variations in the docker compose file, primarily the download URL.

ORG_OPENCASTPROJECT_DOWNLOAD_URL=http://${HOSTIP:-localhost}:18080/static

Changing the download URL appears to cause the error below when the workflow tries to publish

(ConfigurablePublishWorkflowOperationHandler:286) - Start bulk publishing of 1 elements of media package '8f175e2b-80bc-4a2b-ab31-89f6be95cdeb' to publication channel 'internal'
opencast_1  
| 2019-11-13T03:04:24,677 | WARN  | (DownloadDistributionServiceImpl:359) - Error distributing http://localhost:8080/files/mediapackage/8f175e2b-80bc-4a2b-ab31-89f6be95cdeb/fb8e6b36-8925-42e7-a12a-d8a6ff56fb18/1mb.mp4
opencast_1  
| org.opencastproject.security.api.TrustedHttpClientException: java.net.ConnectException: Connection refused (Connection refused)

Any suggestions would be greatly appreciated :-)

Cheers,
Tom

Tom Scott

unread,
Nov 14, 2019, 12:22:23 AM11/14/19
to Opencast Users
Afternoon,

Had a go at flipping to the multi-server docker compose (docker-compose.multiserver.mariadb.yml) but that added more confusion regarding ports with http chatter flipping between docker service names and localhost usages.  It was ended up in the same state with failures to publish.

Will stick with the default ports and try again in the near future.

Regards,
Tom

Greg Logan

unread,
Nov 14, 2019, 5:52:47 PM11/14/19
to Opencast Users
Hi Tom,

I know this (or something very similar) worked at one point since I used to do this without docker for testing clusters. 

Can you file this as an issue on GitHub? I feel like this is more of a docker image issue, but it might be an issue upstream too.

Thanks, 
G

--
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

Tom Scott

unread,
Nov 17, 2019, 8:47:37 PM11/17/19
to Opencast Users
Hi Greg,

Thanks again, I've raised the issue and will look into this a bit more hopefully by the end of the week.

Cheers,
Tom
To unsubscribe from this group and stop receiving emails from it, send an email to us...@opencast.org.

Greg Logan

unread,
Nov 22, 2019, 5:33:04 PM11/22/19
to Opencast Users
Hi Tom,

Finally had a chance to circle round to this, have you updated your workflows to reflect the port changes?  A few of them (notably the ones dealing with ConfigurablePublishWorkflowOperationHandler), have hardcoded 8080s in them...

G

To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

Tom Scott

unread,
Nov 24, 2019, 5:20:12 PM11/24/19
to Opencast Users
Hi Greg,

I tried variations our custom workflow, tenant and environment variables, there's a good chance I inadvertently caused some mismatches in my experimentation.  Not sure I went anywhere near anything dealing with the publish directly, hoping to find some time this week to have a look.

Thank for having a look :-)

Regards,
Tom
Reply all
Reply to author
Forward
0 new messages