Description
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:
docker run -d --name oracle-instance -p 8080:8080 ghcr.io/oracle/nosql:latest-ce
However, with recent changes, this command no longer starts the service correctly.
Steps to Reproduce:
-
Run the following command (as per previous working usage):
docker run -d --name oracle-instance -p 8080:8080 ghcr.io/oracle/nosql:latest-ce
-
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):
docker run -d --name kvlite --hostname=kvlite --env KV_PROXY_PORT=8080 -p 8080:8080 ghcr.io/oracle/nosql:latest-ce
-
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:
- Developer productivity
- Prototyping
- Education and demos
- Lowering the barrier for adoption
It might be related to this bug as well: