codefromthecrypt
commented
3 years ago Our mysql image is not intended for production use, so adding more modules to our image only to support use like this doesn't mix. It adds image size for non-typical and non-production use cases.
I would recommend using a different storage option (such as elasticsearch or cassandra), or make your own image of zipkin based on ours, but includes a full JRE or one jlinked with:
# GSS API auth is used by Azure Database for MySQL Server
java.security.jgss,\Here's a dockerfile you can use to make your own image if you really need to setup a test mysql in azure.
ARG zipkin_version=master
# import Zipkin's official layer
FROM openzipkin/zipkin:$zipkin_version as officialZipkin
# use a larger JRE
FROM azul/zulu-openjdk-alpine:15-jre as zipkin
# Add HEALTHCHECK and ENTRYPOINT scripts into the default search path
COPY --from=officialZipkin /usr/local/bin/docker-healthcheck /usr/local/bin/
HEALTHCHECK --interval=5s --start-period=30s --timeout=5s CMD ["docker-healthcheck"]
COPY --from=officialZipkin /usr/local/bin/start-zipkin /usr/local/bin/
ENTRYPOINT ["start-zipkin"]
# All content including binaries and logs write under WORKDIR
ARG USER=zipkin
WORKDIR /${USER}
# Ensure the process doesn't run as root
RUN adduser -g '' -h ${PWD} -D ${USER}
# Switch to the runtime user
USER ${USER}
# Copy official binaries onto this layer
COPY --from=officialZipkin --chown=${USER} /zipkin/ .
# 3rd party modules like zipkin-aws will apply profile settings with this
ENV MODULE_OPTS=
# Zipkin's full distribution includes Scribe support (albeit disabled)
EXPOSE 9410 9411
welsh
Describe the Bug
When starting the application, the following error is presented:
However the application still appears to function normally and is able to receive / display traces, when connecting using a docker-compose to the same database on Mac 10.15.7 this error doesn't appear.
Steps to Reproduce
Deploy Zipkin onto Azure Kubernetes Service (1.18.8) with Azure Database for MySQL Server (Version: 8.0)
Expected Behaviour
Application should not error upon startup.