Container deployment
A container image has its own version and defaults. Do not assume an older image matches the current binary distribution or the examples in these docs.
Select an image
Section titled “Select an image”Use an image and immutable tag published for the release you intend to run. Verify the server version inside the container. These docs do not prescribe an unverified floating image tag.
For a directly checked local setup, start with binary installation.
Persist data
Section titled “Persist data”Mount persistent storage at the directory passed to --data-dir. Confirm that the server process can read and write it. A container restart must reuse that volume to retain records.
Expose only required endpoints
Section titled “Expose only required endpoints”Use connection addresses for the installed version. Configure the listener inside the container and the published host port separately. Keep credentials and administrative endpoints off untrusted networks.
Health and recovery
Section titled “Health and recovery”Probe the HTTP health endpoint. Test a restart, an application query and your recovery procedure before sending production traffic to the container.
This site uses Google Analytics cookies to count visits. Privacy · License