This is the latest major version of the Otohits App.
docker run \
--name otohits \
--cap-drop=ALL \
--shm-size=1gb \
--security-opt=no-new-privileges \
-e APPLICATION_KEY=<Your_Application_Key> \
otohits/app-next:latest
This release focuses on security hardening and core dependency updates:
root. It now executes under a dedicated unprivileged user, applying the principle of least privilege to keep your host system secure.| Name | Required | Description |
|---|---|---|
--shm-size=1gb | ✓ | Increases shared memory allocation (default is 64MB). Needed for the internal browser to communicate efficiently with its own processes. Note: it simply gives the container room to safely burst if needed. It acts as a max limit, not a reservation, so it only consumes as much RAM as the app actively uses. |
--cap-drop=ALL | ✓ | Improves security. Drops all Linux capabilities (e.g., raw sockets, system administration rights) from the container root user. |
--security-opt=no-new-privileges | ✓ | Improves security. Prevents processes inside the container from gaining additional privileges via setuid or setgid binaries (like sudo or suid). |
-d | The application will run in the background. |
| Name | Required | Description |
|---|---|---|
-e APPLICATION_KEY=<Your_Application_Key> | ✓ | Your application key. Required to send points on your account. |
-e NOLOG=true | The application will not write logs. Consume less space. Make sure the application is working properly before switching it off. | |
-e NOUPDATE=true | The application will not try to update itself. Make sure you still plan to update manually at some point. |
Otohits/app repository currently only has one tag: latest.
Because this new version requires new arguments to function properly, updating latest directly would break existing setups. Instead, we prefer to let users gradually test and transition to Otohits/app-next before eventually decommissioning the old repository.
This image follows a modified Semantic Versioning schema to differentiate between application updates and container infrastructure changes:
MAJOR.MINOR.PATCH (e.g., 1.0.6000)
1.x.x): Reserved for breaking changes in the application or major container environment overhauls that require manual intervention or configuration updates.x.1.x): Incremented for container-level updates (e.g., base OS updates, optimized Docker scripts, environment variable changes, or dependencies) while keeping the underlying application unchanged.x.x.6000): Tracks the upstream application version directly. A patch release guarantees the container layout is identical, but the internal application binary/assets have been updated.latest: Always points to the most recent stable release. Recommended for quick setups, though pin a specific version tag for production stability.X.Y.Z (e.g., 1.0.6000): Immutable release tag matching a specific app version and container build.Content type
Image
Digest
sha256:7b09ca86b…
Size
287 MB
Last updated
about 1 month ago
docker pull otohits/app-next