As much as a memo.
I got moss when I used an existing image
webdizz / centos-java8 when I was brain dead and created a java8 environment on centos. You shouldn't skip this kind of thing. Don't use something you don't understand.
Below is the detailed Java version
# java -version java version "1.8.0_11" Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
When I do
digdag push, I get a log with a time stamp, but it seems that the cause was that the API of the Java time-related library did not work well at that time.
ʻUnable to obtain Instant` I was getting an error saying ...
By the way, it worked fine in the following versions.
# java -version openjdk version "1.8.0_171" OpenJDK Runtime Environment (build 1.8.0_171-b10) OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode)
Install with Dockerfile looks like this
FROM centos:latest RUN \ yum update -y && yum install -y \ java-1.8.9-openjdk \ java-1.8.0-openjdk-devel
There was no problem with Java, and I thought that the setting of
JAVA_HOME was wrong, so I set it again and tried it, but it was reproduced after all, so it seems that the java version was not good.
There may be other solutions, so please let me know if this is the case.
According to the description of the official document that you told me in the comment section, Java8 u72 or later is required to run digdag.
The version of Java at the time of the problem was certainly older than u72 when examined.