error by getting CONTAINER_MAX_MEMORY since last image

[abinet]

For image based on fabric8/java-jboss-openjdk8-jdk:1.2.7 container-limits script does not work properly since last changes when '/sys/fs/cgroup/memory/memory.memsw.limit_in_bytes' does not exist:

$ source /deployments/container-limits
cat: /sys/fs/cgroup/memory/memory.memsw.limit_in_bytes: No such file or directory
bash: [: 1999998976: unary operator expected

That leads to lack of -Xmx by java default options

[rhuss]

Thanks for pointing this out. How and where did you call this image so that this file in missing ?

The latest update of run-java.sh takes care of it, it just requires a new release of these images. This will happen soon.

[abinet]

Thanks for the answer.
The containers are running on Rancher cluster with Kubernetes 1.5.

So until next release I can just use fabric8/java-jboss-openjdk8-jdk:1.2.6 as a base