-
Notifications
You must be signed in to change notification settings - Fork 5.5k
🐳 Regression: Oracle NoSQL Docker image no longer works with single docker run command #2974
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
Comments
I am running the commands you are providing, and it works
Validating the kvlite and the proxy started
Validating the communication intra containers - printing the version, the current tables
Validating that port 8080 is exposed and working
Download, unzip NoSQL SDK for Java and compile the NoSQL SDK for Java examples. We will use java programs to test the configuration. Other language SDKs are available which you can use, however, we are providing Java examples.
Test using the example provided in the Oracle NoSQL SDK
Could you validate the same steps? |
NB: It is not related to #2972 - not the same product. |
Description:
Previously, we could run a local Oracle NoSQL instance quickly using a single Docker command. This was extremely helpful for local development and trying out NoSQL features before using the cloud service.
The original command worked flawlessly:
However, with recent changes, this command no longer starts the service correctly.
Steps to Reproduce:
Run the following command (as per previous working usage):
Notice that the container does not start properly or does not expose the expected service on
http://localhost:8080
.Tried the updated version from the [official README](https://github.com/oracle/docker-images/blob/main/NoSQL/README.md):
Still does not respond or expose the expected proxy endpoint.
Expected Behavior:
A local instance should be accessible via a simple Docker command, as before. This makes it easy for developers to test Oracle NoSQL locally before integrating with cloud services.
Actual Behavior:
The Docker container starts (in some cases), but no service is available on port 8080. The original convenience of quick start via a single command has been broken.
Why This Matters:
The ability to spin up a local NoSQL instance with a one-liner Docker command is essential for:
It might be related to this bug as well:
#2972
The text was updated successfully, but these errors were encountered: