-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start app in read only mode #91
Comments
I'm having the same issue with schema-registry-ui/docker/Dockerfile Line 16 in c99eb61
|
Same issue, readonly mode not functional. |
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:
|
I've created a secondary Docker image that build the application from the source (no local dep), hope it helps - |
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
The text was updated successfully, but these errors were encountered: