Create an Always-on Container
Nexaa’s Always-On Containers are designed for applications that require a persistent, always-available runtime environment. Unlike event-based or short-lived container jobs, Always-On Containers stay up to continuously serve requests, process events, or maintain stateful connections. They are ideal for APIs, web servers, microservices, and background services that require uninterrupted availability and predictable performance.
This guide walks you through creating your first container job using the Nexaa portal.
Prerequisites
- A Nexaa account with billing completed.
- A container image that performs the task you want to schedule (must be hosted in a public or authorized registry).
- Optional: A private registry configured in your Namespace if your image is private.
Step 1: Log In
Go to the nexaa portal and sign in using your Nexaa credentials.
Step 2: Navigate to Your Namespace
- From the dashboard, select your Namespace or create a new one.
- Go to the tab "Containers".
Step 3: Create a Container
- Click "Add Container".
- Fill in the following fields:
| Field | Description |
|---|---|
| Container Name | A unique identifier for your job (e.g. daily-report) |
| Container Image | The image you want to run (e.g. my-org/reporter:latest) |
| Registry Credentials | The registry source of where your image is stored |
| Resource | Select the required resources for your job |
| Environment Variables | Key-value pairs for environment variables |
| Expose Port | Expose the port within the namespace on which the container is accessible |
| Internet accessibility | Configure ingress to accept internet traffic to this container |
| Persistent Volume | Mount an existing or new persistent volume |
| Health Check | Provide an endpoint that will return a HTTP status code in the 200 range to validate liveness |
| Scaling | Configure how to scale, manual or automatic |
Step 4: Save and Deploy
- Click "Create Container"
Tips & Best Practices
- See API call before deploying you can view how you can recreate the container with an API call.
- Test your image manually before deploying to avoid runtime surprises.
- Avoid writing to the container filesystem — use external storage or databases.
- Use secrets for any credentials instead of hardcoding environment variables.