Deploy an existing image
Use an image deployment when your delivery process already produces a runnable Docker-compatible image.
Prepare the image
Before opening Infralane, verify that the image:
- starts the intended application process by default;
- uses a stable, explicit tag for production releases;
- listens on the port you will configure for a web service;
- does not contain credentials or private keys;
- writes useful runtime information to standard output and errors;
- stores durable data only in an intended persistent volume.
Avoid relying on a moving tag such as latest for a release that must be reproducible. An explicit version tag makes returning to a known source version and reviewing incidents clearer.
Choose Docker Image
Open Applications → Deploy application, enter the application name and description, then select Docker image.
Enter the image reference
Provide the complete registry path and tag, for example registry.example.com/team/api:2026-09-05. Use only an image the workspace is authorized to deploy.
Select registry access
Leave Public image (no credentials) selected for a public image, or choose a private registry credential granted to this project. Credentials are saved through workspace integrations; do not include them in the image reference. On ARM servers, the image must support the server architecture.
Choose the application type
Select Web service or Static site for an image serving HTTP, Background worker for continuous background work, or TCP/UDP service for a non-HTTP listener. The image must already contain its server and entrypoint; static image deployments do not run the source static-site builder.
Configure the port
Web services require the port used inside the running application. Workers do not use a port. The configured port must match the application’s actual listener.
Choose capacity and runtime values
Select a resource pool plus CPU and memory. Add environment variables or persistent volumes as required.
Review and deploy
Verify the image registry, repository, tag, application type, port, and resource allocation. Select Deploy application, then follow the deployment until it is live or provides an actionable error.
Image-pull failures
If Infralane cannot pull an image:
- confirm the registry hostname, repository path, and tag;
- confirm that the tag exists and is published for the expected architecture;
- for a private image, check the selected registry credential, project grant, pull permissions and token expiry;
- publish a new version rather than overwriting a known-good production tag;
- retry only after correcting the cause.
Do not paste registry passwords or access tokens into a support message. Share only the non-secret image reference and customer-facing error.