lensesio / schema-registry-ui

Web tool for Avro Schema Registry |
http://lenses.io/product/features
420 stars 112 forks source link

Cannot start app in read only mode #91

Open marascha opened 4 years ago

marascha commented 4 years ago

I need to run the app in the read only mode so that new schemas cannot be created and existing ones can not be edited. Nevertheless, I'm not able to start the app in read only mode.

Env Properties: SCHEMAREGISTRY_URL: http:// ... PROXY: true READONLY_MODE: 1

Due to the logs the application starts in read only mode:

Landoop Schema Registry UI 0.9.5 Visit <https://github.com/Landoop/schema-registry-ui/tree/master/docker> to find more about how you can configure this container. Enabling readonly mode. Setting Schema Registry URL to http://... │ Note: if you use a PORT lower than 1024, please note that schema-registry-ui can now run under any user. In the future a non-root user may become the default. In this case you will have to explicitly allow binding to such ports, either by setting the root user or something like '--sysctl net.ipv4.ip_unprivileged_port_start=0'. Activating privacy features... done. http://0.0.0.0:8000 ...

Nevertheless, I can create new Schemas and edit existing ones in the app...

Would be great if could help me with this

seruman commented 4 years ago

I'm having the same issue with landoop/schema-registry:{0.9.5, latest}. Apparently it's fixed in master and latest image built from c99eb61be6a57260fed67392efadee3b76d65677. Since in Dockerfile it's downloading a specific version (which 15 commits behind master) instead of building from source, latest image also has this issue. https://github.com/lensesio/schema-registry-ui/blob/c99eb61be6a57260fed67392efadee3b76d65677/docker/Dockerfile#L16

diseku commented 4 years ago

Same issue, readonly mode not functional. Any plans for new release?

kmcminn commented 4 years ago

just patched this in my private docker registry. This is fixed on master but unreleased as mentioned.

to make a local build you'll need node11 w/ npm6 (node12 is prob ok also) and then:

then use this modified Dockerfile:

ENV SCHEMA_REGISTRY_UI_VERSION="master"
WORKDIR /

RUN apk add --no-cache ca-certificates wget && \
    echo "progress = dot:giga" | tee /etc/wgetrc

RUN wget "https://github.com/mholt/caddy/releases/download/v0.10.11/caddy_v0.10.11_linux_amd64.tar.gz" -O /caddy.tgz && \
    mkdir caddy && \
    tar xzf caddy.tgz -C /caddy --no-same-owner && \
    rm -f /caddy.tgz

COPY dist/ /schema-registry-ui
RUN rm -f /schema-registry-ui/env.js && ln -s /tmp/env.js /schema-registry-ui/env.js
ADD docker/Caddyfile /caddy/Caddyfile.template
ADD docker/run.sh /
RUN chmod +x /run.sh
EXPOSE 8000
ENTRYPOINT ["/run.sh"]
EladLeev commented 2 years ago

I've created a secondary Docker image that build the application from the source (no local dep), hope it helps - https://github.com/lensesio/schema-registry-ui/pull/112