Free tools Windows power users keep installed
One-click scans. No signup required.
To deploy an existing image on Coolify, create a Docker Image resource, point it at the image repository with a release tag or digest, set the container’s internal port, configure any domain and runtime settings, then save and deploy. Coolify pulls the image on the selected server and runs it; this resource does not clone a Git repository or build a Dockerfile.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
What a Coolify Docker Image deployment does
A Docker Image resource is for an image that already exists in a registry such as Docker Hub or a private container registry. Coolify instructs Docker on the deployment server to pull that reference, creates the container, and applies settings such as environment variables, ports, health checks, storage, networks, and restart behavior.
As an Amazon Associate I earn from qualifying purchases.
The image remains responsible for its own filesystem and default process. Coolify supplies the runtime configuration around that process. Because the container can be replaced during a deployment or restart, data that must survive replacement belongs in configured persistent storage rather than only in the container’s writable filesystem.
This is different from the other common deployment paths:
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Deployment path | What Coolify does | Best fit | Reference control |
|---|---|---|---|
| Docker Image | Pulls and runs an existing registry image | One application image that is already built | A tag or SHA256 digest stored with the resource |
| Dockerfile | Builds an image from source and a Dockerfile | When the application source must be built by Coolify | The source revision and Dockerfile build result |
| Docker Compose | Manages a Compose-defined group of services | Applications requiring multiple coordinated containers | The Compose configuration and each service image |
A Docker Image resource therefore makes the registry image the deployable artifact while Coolify owns how that artifact is started and exposed.
Prerequisites and information to collect
- Access to a Coolify dashboard.
- At least one connected server selected as the deployment target.
- A running Coolify proxy if the application will be reached through a domain.
- The complete image name, including its registry hostname when it is not Docker Hub.
- Either a release tag, such as
1.4.0, or a SHA256 digest for the exact image content. - The internal container port on which the application listens.
- Registry credentials on every server that must pull the image when the repository is private.
If you want a basic connectivity smoke test before deploying your own application, Coolify’s first-app walkthrough uses nginx:alpine and internal port 80. That test confirms that the server, proxy, and generated test domain are working before application-specific configuration is introduced.
Deploy the image step by step
1. Open the target project and environment
In the Coolify dashboard, open the project and environment where the resource should live. Choose the connected server that has network access to the registry. A private image will not deploy unless that server has permission to pull it.
2. Create a Docker Image resource
Select + New → Docker Image. This resource type tells Coolify to pull an existing image rather than looking for source code or a Dockerfile.
3. Enter the image reference
You can provide a complete reference such as ghcr.io/example/api:1.4.0. If the interface presents separate fields for the repository and version, enter the repository and complete either the Tag field or the SHA256 Digest field. Do not fill in both.
When using the separate digest field, enter the 64-character hexadecimal digest without the sha256: prefix. A malformed digest, a tag that does not exist, or a repository name that is missing its registry hostname will cause the pull step to fail.
4. Set the internal port
Open General and set Ports Exposes to the port used by the process inside the container. Docker Image applications start with port 80 as the default, so change this value when the image listens on another port, such as 3000 or 8080.
This is the container’s internal listening port, not an assumption that the host’s public port will be identical. Coolify’s proxy uses the configured domain and routes traffic to the container through this setting. If the process listens on 3000 but Ports Exposes remains 80, the container may appear to be running while requests fail.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
5. Add a domain when the service is public
Add the domain or generated test domain in the resource’s domain settings when users must reach the application over HTTP or HTTPS. The proxy then routes that hostname to the configured container port. A service that is intended only for an internal network can omit a public domain and use its configured network connection instead.
6. Configure runtime values
Add the environment variables the application expects, then configure persistent storage, health checks, resource limits, and other runtime options as needed. These values change how Coolify starts the container; they do not modify the image stored in the registry.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallEnvironment variables are stored separately from the running container. After changing them, save the resource and restart or redeploy it so Coolify recreates the runtime with the new values. If a value was needed while an image was being built, changing it at runtime cannot retroactively change that image; build-time values require a new image build through an appropriate source-based deployment.
7. Save and deploy
Select Save, then Deploy. Open the deployment logs and verify that Coolify pulled the intended repository and reference, created the container, and started it without an immediate exit. Once deployment completes, open the configured domain and inspect the application logs for startup errors, migrations, or missing configuration.
What happens during a deploy or restart
Coolify uses the saved image reference on the selected server. Docker pulls the image when it is not already available locally, then Coolify prepares the container with the saved environment variables, port mapping, networks, storage, restart behavior, limits, and health-check configuration. The container is then created or replaced and started with the image’s default process unless the image and runtime settings specify otherwise.
A restart is not necessarily a “run the exact bytes already on disk” operation. For a Docker Image application, Coolify pulls the saved reference again. With a digest, that reference continues to identify the same image content. With a mutable tag, the registry can resolve the same text to newer content. This is why a restart can expose an image change even when no Coolify field was edited.
Runtime edits follow the same recreation model. Saving a new variable, port, domain, health check, storage mount, or limit changes the resource configuration, but the already-running process does not receive those values automatically. Restart or redeploy after saving so the container is created with the updated runtime envelope.
Choosing a tag or a digest
Version tags
A release tag such as 1.4.0 is easy to read and practical when your registry treats release tags as immutable. It communicates the intended application version in the Coolify interface and deployment history.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
SHA256 digests
A digest identifies the image content itself. If the repository uses tags that can be moved, a digest provides the most precise reference because it continues to identify the same image manifest and layers.
Why latest can surprise you
A mutable tag such as latest can point to different content later. Coolify saves the reference, and restarting a Docker Image application pulls that saved reference again. If the tag was moved in the registry, a restart can therefore run different bytes even though the Coolify configuration was not edited.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →For production, use a release tag that your release process does not rewrite or pin the resource to a digest. Use mutable development tags only when that change-on-pull behavior is deliberate.
Runtime settings that determine whether the container works
Ports and routing
The application must bind to the port you expose inside the container and, for a proxied HTTP service, to an interface reachable from the container network. Confirm the listening port from the image documentation or its startup configuration rather than assuming that every web image uses port 80.
The domain belongs to Coolify’s routing layer. It does not rewrite the application’s internal port. A correct domain with an incorrect Ports Exposes value still sends traffic to the wrong destination.
Environment variables
Define secrets, database URLs, hostnames, and feature flags in the resource’s environment settings instead of baking changing values into the image. Save the settings and redeploy or restart after edits; the already-running process does not receive newly saved variables automatically.
Persistent storage
Mount configured storage for uploads, databases, caches that must survive replacement, or any other durable state. A deployment can replace the container, so files written only into its writable layer should be treated as disposable.
Restart behavior, networks, and limits
Coolify prepares restart behavior, networks, resource limits, ports, and health checks before Docker creates or replaces the container. Set limits when the service needs predictable resource boundaries, and attach the networks required to reach dependent services. These controls surround the image; they do not add packages or alter its default process.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Health checks: configure them without creating false failures
Coolify-managed checks can be HTTP checks or CMD checks. An HTTP check executes inside the application container, so the final image must contain curl or wget. Minimal images often omit both utilities, which makes an otherwise healthy process appear unhealthy.
The check’s endpoint and port must match the process inside the image. For an application that listens on port 3000 and exposes a /health endpoint, a Dockerfile pattern is:
HEALTHCHECK --interval=30s --timeout=5s --start-period=20s --retries=3 CMD curl --fail http://localhost:3000/health || exit 1This is a pattern, not a universal endpoint. Use the path your application actually serves. The start period gives a slow-starting process time to become ready; the timeout and retry values determine how quickly transient failures are treated as unhealthy.
After enabling, changing, or disabling a health check, restart or redeploy the resource so Coolify recreates the container with the new check. If the check fails, first run the same URL or command in the container context, then verify that the process is ready at that path and that the required utility exists in the image.
Verify a deployment before calling it complete
- Read the deployment log and confirm the repository and tag or digest are the ones you intended.
- Confirm the container reaches its running state instead of repeatedly exiting and restarting.
- Check that Ports Exposes matches the process’s internal listening port.
- Open the configured domain or generated test domain and verify the expected response.
- Review application logs for configuration errors that a successful image pull cannot reveal.
- If a health check is enabled, wait for it to report ready and verify its endpoint independently.
- Restart the resource once in a non-production window if you need to confirm that persistent storage and startup configuration behave as expected.
Troubleshooting by symptom
The image pull fails
- Check the repository spelling and registry hostname.
- Verify that the tag exists or that the digest is exactly 64 hexadecimal characters without the
sha256:prefix in the separate digest field. - For a private repository, confirm that credentials are configured on the specific deployment server, not only on another server in the Coolify installation.
- Read the deployment log for an authentication, authorization, manifest, or network error; each points to a different registry-side problem.
The container starts but the domain is unreachable
- Confirm that the process is listening on the port entered in Ports Exposes.
- Check that the domain is attached to this resource and that the Coolify proxy is running.
- Inspect application logs for a process bound only to an unexpected address or for a startup failure after the container was created.
The health check stays unhealthy
- Test the exact endpoint and internal port used by the check.
- Make sure the process is ready at that path rather than merely started.
- Install or include
curlorwgetin the final image when using an HTTP check. - Redeploy or restart after changing the check so the container is recreated.
A changed variable is not visible
Save the environment setting and redeploy or restart the resource. Coolify stores variables outside the running container, so editing the dashboard value alone does not mutate the process that is already running.
Recommended Free Tools
A restart produced unexpected application changes
Inspect the saved image reference. If it uses a mutable tag, the registry may now resolve that tag to newer content. Replace it with an immutable release tag or a digest when repeatable restarts matter.
Production checklist
- Use a release tag that is not rewritten, or pin the image by digest.
- Record the internal listening port and set Ports Exposes to that value.
- Authenticate every server that may deploy the private image.
- Keep durable data in configured persistent storage.
- Store runtime configuration in Coolify and recreate the container after changes.
- Only enable an HTTP health check when the image contains
curlorwgetand serves the selected endpoint. - Review deployment and application logs after the first deployment and after reference changes.
- Test the domain through the Coolify proxy, not only the container’s local process.
When a Docker Image resource is the wrong choice
Choose a Dockerfile deployment when Coolify must build the image from application source, install dependencies, or incorporate a source revision as part of deployment. Choose Docker Compose when the application is a group of services that must be created and networked together. A Docker Image resource is intentionally narrower: it pulls one already-built image and supplies its runtime envelope.
Final recommendation
For a reliable Coolify deployment, start with a known image reference, expose the container’s actual internal port, configure the domain and runtime values, persist required data outside the container, and verify the pull, startup, health, and proxy path in the logs. Pin production deployments to a stable release tag or digest so a later restart does not silently select different image content.
Frequently Asked Questions
Can Coolify deploy an image from Docker Hub?
Yes. Create a Docker Image resource and enter the image name and tag, such as nginx:alpine. If the image is private, configure registry credentials on the server that will perform the pull.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow do I deploy an image from GHCR?
Enter the complete GHCR reference, for example ghcr.io/example/api:1.4.0, then select the tag or digest and configure credentials on each deployment server that needs access to the private repository.
What does Ports Exposes mean in Coolify?
It is the port where the process listens inside the container. It is not automatically the host’s public port. Set it to the application’s actual internal port, such as 3000 or 8080, when it is not port 80.
Should I use a tag or a SHA256 digest?
Use a release tag when your registry does not rewrite it and readability is useful. Use a digest when you need the image content pinned exactly. In the separate digest field, enter 64 hexadecimal characters without the sha256: prefix, and do not fill the tag field at the same time.
Why did restarting the application pull different image content?
Coolify pulls the saved image reference again on restart. If that reference is a mutable tag such as latest, the registry may have moved it to newer content. Replace it with a stable release tag or digest for predictable restarts.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why is my container running but the domain does not respond?
Check that Ports Exposes matches the process’s internal listening port, that the domain is attached to the resource, and that the Coolify proxy is running. Then inspect application logs for a startup error or an unexpected bind address.
Why does an HTTP health check fail on a healthy image?
The check runs inside the container. Confirm that the endpoint and port are correct and that the final image contains curl or wget. Restart or redeploy after changing the check so Coolify recreates the container.
Do environment-variable edits change a running container immediately?
No. Coolify stores those values separately from the running container. Save the change and restart or redeploy so the process starts with the new environment.
Where should application data be stored?
Use configured persistent storage for data that must survive a deployment or container replacement. Files written only to the container’s writable filesystem should be considered disposable.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →When should I use Dockerfile or Compose instead?
Use Dockerfile when Coolify must build an image from source. Use Docker Compose when several coordinated services must be created and networked together. Use Docker Image when one already-built registry image is the deployable artifact.
The Bottom Line
Bottom line: Create a Docker Image resource, use a complete registry reference with a stable tag or digest, set the real internal port, configure runtime settings and persistent storage, then deploy and verify the logs, health check, and proxy route. Pin production images instead of relying on latest.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
