Check whether the startup warnings for unknown modules represent a legit problem or cosmetic issue

Launched a tarball-based 5.0-alpha2 container on top of
"eclipse-temurin:17-jre-focal" and the server starts up fine, can run
nodetool and cqlsh.
I got these seemingly harmless JDK17 warnings during startup and when
running nodetool (no warnings on JDK11):
WARNING: Unknown module: jdk.attach specified to --add-exports
WARNING: Unknown module: jdk.compiler specified to --add-exports
WARNING: Unknown module: jdk.compiler specified to --add-opens
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by
org.apache.cassandra.security.ThreadAwareSecurityManager
(file:/opt/cassandra/lib/apache-cassandra-5.0-alpha2-SNAPSHOT.jar)
WARNING: Please consider reporting this to the maintainers of
org.apache.cassandra.security.ThreadAwareSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
Anybody knows if these warnings are legit/expected ? We can create
follow-up tickets if needed.
$ java --version
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode,
sharing)

Clarification: - When running nodetool only the "Unknown module" warnings show up. All warnings show up during startup.