Docker container images are broken - missing Siena modules

[openseedbox]

Docker container images are broken - missing Siena modules

[xabolcs]

Yeah ... www.playframework.com updated it's https configuration and old urllibs die.
I faced with too.

The related issue what you also found is playframework/play1#1126.

The workaround for Dockerfile doesn't helps setting up the development environment.

[gregorkistler]

True, didn´t notice that you posted the last comment, was more busy with the content of it :)

I personally work around the issue that way since at least one year maybe even two as it never worked out of the box for me.
Always had a non-resolvable Siena module dependency issue.

Let´s see what the guys over at Play! Framework will do.

[xabolcs]

Fix is coming. 👍

[xabolcs]

Workaround commit 58a15b8 is pushed.
It's time to update Docker Hub.

[xabolcs]

@erindru please update images at Docker Hub, thanks!

[gregorkistler]

Guess the dependency cleanup in the server code with commit openseedbox/openseedbox-server@3684cad was a little bit too much :)

Output of the openseedbox-server Play! application:

12:14:23,900 INFO ~ Precompiling ...
12:14:25,623 ERROR ~

@73p24golk
Cannot start in PROD mode with errors

Compilation error (In {module:openseedbox-common}/app/com/openseedbox/backend/NodeStatus.java around line 3)
The file {module:openseedbox-common}/app/com/openseedbox/backend/NodeStatus.java could not be compiled. Error raised is : siena.embed.EmbeddedMap cannot be resolved

play.exceptions.CompilationException: siena.embed.EmbeddedMap cannot be resolved
...

Frontend looks good now.

Actually we could place the Siena module in the openseedbox-common repo and point both (client and server) dependencies.yml to something like this:

- offlinePlayRepo:
       type: local
       artifact: ${application.path}/../openseedbox-common/play-offline/[module]-[revision].zip
       contains:
          - playOffline

That´s at least what I do currently.

[xabolcs]

All Docker images should be functional!

[gregorkistler]

I´ve pulled the latest images from Docker Hub a couple of minutes ago but the server image still doesn´t work correctly.
Siena module dependency was fixed so we could close this one here if needed and create a new one based on the following error:

18:01:01,384 ERROR ~ 

@73pbkpf8a
Cannot start in PROD mode with errors

Compilation error (In /app/com/openseedbox/backend/transmission/TransmissionBackend.java around line 158)
The file /app/com/openseedbox/backend/transmission/TransmissionBackend.java could not be compiled. Error raised is : The method encodeBase64String(byte[]) is undefined for the type Base64

play.exceptions.CompilationException: The method encodeBase64String(byte[]) is undefined for the type Base64
	at play.classloading.ApplicationCompiler$2.acceptResult(ApplicationCompiler.java:246)
	at org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:676)
	at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:520)
	at play.classloading.ApplicationCompiler.compile(ApplicationCompiler.java:282)
	at play.classloading.ApplicationClassloader.getAllClasses(ApplicationClassloader.java:426)
	at play.Play.preCompile(Play.java:603)
	at play.Play.init(Play.java:307)
	at play.server.Server.main(Server.java:162)

Issue #14 was about the same and provides a solution by adding - commons-codec -> commons-codec 1.7 back into the dependencies.yml
The odd thing about the error is that I had it once during the last few days but currently cannot reproduce it.
Code from the repo works solid on different hosts and docker-compose setups.

Java version related?
The Docker image uses OpenJDK 1.6.0_38
I´ve successfully tested it with 1.6.0_41, 1.7.0_121 and 1.8.0_111 as well as 1.8.0_121

[xabolcs]

Docker sucks and I'm noob.
How do you refresh / rebuild your Docker containers? Try --pull and --no-cache options!

This common-codec stuff is caused by the siena dependencies in openseedbox-common which should be fixed by the latest commit openseedbox/openseedbox-common@020990f.

[xabolcs]

Linked (and retriggered) openseedbox/server automated build to openseedbox/client, hope this helps.

Link your Automated Build to another Docker Hub repository, and when that repository is updated, it will automatically trigger a rebuild of this Automated Build.

[gregorkistler]

I actually just delete the related container and images and use docker run to pull it completely from Docker Hub again.

One of the latest two builds fixed the issue :)
Backend runs as expected again.

[xabolcs]

docker pull && docker run is my new friend. :)

Thanks for the feedback.