Skip to content

Commit

Permalink
Maybe --initialize-at-build-time should be removed after we've tracked
Browse files Browse the repository at this point in the history
down after we've resolved classpath issues.

The stdout prints of config are gone now, but this print remains:
INFO org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
  • Loading branch information
solsson committed Aug 16, 2020
1 parent 9826bff commit e8da8a7
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions native/zookeeper-server-start.Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,9 @@ RUN native-image \
--initialize-at-run-time=org.apache.zookeeper.server.persistence.FileTxnLog \
--initialize-at-run-time=org.apache.zookeeper.server.persistence.TxnLogToolkit \
--initialize-at-run-time=org.apache.zookeeper.server.persistence.FilePadding \
# Can we instantiate at build time things that depend on config file contents?
--initialize-at-run-time=org.apache.zookeeper.server.quorum.Leader \
--initialize-at-run-time=org.apache.zookeeper.server.ZooKeeperServer \
# Added because of io.netty.buffer.Unpooled.wrappedBuffer(byte[]), org.eclipse.jetty.servlet.ServletContextHandler.<init>(int)
--allow-incomplete-classpath \
# -D options from entrypoint
Expand Down

0 comments on commit e8da8a7

Please sign in to comment.