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 rollback and incident review 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.
Choose the application type
Select Web Service for an HTTP process, Static Site for an image used according to that workflow, or Background Worker for a process without a public port.
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 app, 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;
- check whether the image is private and whether the workspace has a supported way to access it;
- 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.