The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Set container runtime flags in Coolify’s General > Custom Docker Options field, save the application, and then deploy or restart it. Coolify accepts an allowlist of Docker options—not every flag supported by docker run. For example, --shm-size 1g --init is valid; an unrelated or unsupported flag is ignored rather than passed through to the container.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
The reliable workflow is to decide whether a setting belongs to image construction, application configuration, or container runtime. Put build instructions in a Dockerfile, service behavior in your Compose file, and supported runtime flags in Custom Docker Options or the corresponding Coolify setting. After changing anything that affects the container, redeploy and verify the generated container through deployment logs and application behavior.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 matchWhat Custom Docker Options control
Custom Docker Options is a runtime interface for the container Coolify creates. It changes how an already-built image runs: for example, its shared-memory size, Linux capabilities, DNS configuration, hostname, entrypoint, or device access. Coolify translates only its supported options into the generated container configuration. It does not act as a free-form replacement for every argument accepted by the Docker command-line client.
This restriction protects configuration that Coolify manages itself, including networks, storage mounts, lifecycle operations, domains, health checks, and other deployment details. Passing arbitrary flags could conflict with those systems. If a flag is not on Coolify’s supported list, adding it to the field will not make it active in the resulting container.
#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.
Use the field only when the option belongs to the container runtime. The same principle is expressed in Coolify’s documentation: “Use this field only when the option belongs to the container runtime.”
Supported options
Coolify’s allowlist contains the following Docker runtime options. Enter one or more options in the field, separated as you would provide them to Docker.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Option | Runtime concern | Typical reason to use it |
|---|---|---|
--ip |
IPv4 address | Give the container a specific IPv4 address when the deployment’s network arrangement requires it. |
--ip6 |
IPv6 address | Assign a specific IPv6 address in an IPv6-capable network. |
--shm-size |
Shared-memory allocation | Increase the container’s /dev/shm space for software that uses shared memory. Example: --shm-size 1g. |
--dns |
Container DNS resolver | Supply a resolver address required by the application’s runtime environment. |
--cap-add |
Linux capabilities | Add a narrowly scoped kernel capability needed by a process. |
--cap-drop |
Linux capabilities | Remove capabilities that the container does not need. |
--security-opt |
Security profile | Adjust a supported container security option. |
--sysctl |
Kernel parameter namespace | Set a permitted namespaced kernel parameter for the workload. |
--device |
Host device access | Expose a required host device inside the container. |
--ulimit |
Process resource limits | Raise or constrain a process limit such as open files when the workload requires it. |
--init |
Process supervision | Run an init process as PID 1. Example: --init. |
--privileged |
Container privileges | Run with broad privileges only when the workload cannot function with narrower permissions. |
--gpus |
GPU access | Request GPU resources at container runtime when the host and deployment support them. |
--hostname |
Container hostname | Set the hostname visible from inside the container. |
--entrypoint |
Startup executable | Replace the image’s default entrypoint with a specific executable. |
The table identifies what each allowlisted option changes; it does not grant access to host resources that the server, Docker installation, or Coolify deployment has not made available. For example, --gpus still requires a usable GPU runtime on the connected server, and --device requires the referenced device to exist and be accessible there.
How to add a custom option in Coolify
- Open the application. In the Coolify dashboard, open the target application whose container should receive the option.
- Open the runtime field. Go to General > Custom Docker Options.
- Enter supported arguments. Add one or more allowlisted options. Coolify’s official example is
--shm-size 1g --init. Keep values and their units in the normal Docker form. - Save the application. Saving records the desired configuration, but it does not necessarily replace the container that is already running.
- Deploy or restart. Run a deployment or restart so Coolify creates or starts the container with the new runtime configuration.
- Verify the result. Read the deployment log, then inspect runtime logs and the application’s behavior. Check the specific symptom the option was intended to change rather than assuming that a successful save proves the flag was applied.
If the option affects image construction rather than runtime, this procedure is the wrong tool. Move that instruction into the Dockerfile or Compose build configuration instead.
Choosing the right configuration layer
Coolify deployments combine several layers. Assigning a setting to the wrong layer is the most common reason a Docker option appears to be ignored.
Use a Dockerfile for image construction
A Dockerfile defines the image itself: its base image, operating-system packages, copied application files, build stages, runtime user, and default command. These instructions run while Coolify builds the image. They are not equivalent to flags that Docker applies when it creates a container.
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.
Use the Dockerfile when the requirement must be present in the image for every environment, such as installing a system library, copying a startup script, choosing a base image, creating a user, or defining a default command. A runtime flag cannot install a package or alter files that were never included in the image.
Use the application’s Coolify settings for managed resources
Use dedicated Coolify controls for CPU, memory, GPU, ports, storage, and environment variables when the control exists there. These settings are integrated with Coolify’s deployment model and are easier to inspect than an equivalent hand-written command-line argument.
Although --gpus is on the Custom Docker Options allowlist, a deployment that has a dedicated GPU control should use that control when it expresses the requirement. Reserve the custom field for a runtime option that Coolify does not expose more directly, or for a precise Docker runtime value you intentionally need.
Use Custom Docker Options for runtime behavior
Choose the custom field for supported flags that alter the running container: shared memory, capabilities, security options, sysctls, device mappings, ulimits, initialization, privilege mode, GPU runtime arguments, hostname, IP settings, or entrypoint selection. Coolify then incorporates those values into the generated container configuration alongside its own networks, storage, domains, health checks, and lifecycle settings.
Use Compose for service topology and service commands
For a Git-based Docker Compose application, the Compose definition controls service images, builds, commands, environment references, volumes, health checks, dependencies, and networking. If the requirement describes how multiple services connect or how a service is built, Compose is the natural home for it.
Coolify can inject application build variables as Docker build arguments. That is different from a runtime option: a build argument exists during image creation, while a custom Docker option is applied when the container starts.
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
Dockerfile applications: ports and process binding
When deploying an application built from a Dockerfile, set Ports Exposes to the internal port on which the process listens. This is the port inside the container, not necessarily the public port a visitor uses.
The process must bind to 0.0.0.0. A process listening only on 127.0.0.1 is reachable from inside its own container but not from Coolify’s proxy, so a deployment can appear healthy while the domain returns a connection failure. A custom entrypoint or command must preserve the application’s normal startup and binding behavior; changing the entrypoint does not automatically correct a process that listens on the wrong interface.
Compose applications: commands, files, and paths
Coolify parses a Compose definition and uses it to build and start the services. You can provide a Custom Build Command or Custom Start Command, but each replaces the normal Compose command rather than adding a small fragment to it.
Coolify injects the Compose-file and environment-file flags into those commands unless your custom command supplies its own. Therefore, a replacement command must still identify the correct Compose file and environment file when it invokes Compose directly. Omitting either can cause Coolify to build the wrong service, miss variables, or start with a different topology from the one shown in the dashboard.
Keep paths relative to the application’s Base Directory, and use the same Compose definition that Coolify parsed. A command that works from a developer workstation but assumes a different working directory can fail during deployment because relative paths resolve from the Base Directory.
Custom Docker Options remain a runtime layer around this Compose deployment. They do not replace service-level settings such as volumes, dependencies, health checks, or networking that belong in the Compose file.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
Common examples
Increase shared memory and add an init process
Browser automation, data-processing tools, and other workloads may need more shared memory than the default container allocation. Enter:
--shm-size 1g --initSave, deploy, and check the deployment and runtime logs. The first option changes the container’s shared-memory allocation; the second requests an init process to handle child processes and signal forwarding. If the application still fails, confirm that the failure is actually related to shared memory or process reaping rather than an image, port, or environment problem.
Override an image entrypoint
Use --entrypoint when the image’s built-in startup executable is not the one the deployment should run. This is a runtime override; it does not modify the image and does not automatically supply arguments expected by the replacement executable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
After deploying, inspect logs for an executable-not-found error, permission error, or an application that exits immediately. If the replacement program is not present in the image, rebuild the image with the required file or package in the Dockerfile.
Request GPU access
Use the allowlisted --gpus option only when the connected server has the necessary GPU hardware and container runtime support. The option requests access; it cannot install host drivers or create a GPU where none exists. Confirm the application image contains compatible user-space libraries and verify access in the application’s own startup output.
Grant a device or capability
--device exposes a host device, while --cap-add adds a Linux capability. Both expand what a process can do and should be limited to the exact requirement. If a workload can run without them, do not add them merely because they are available. A narrowly scoped capability or device is preferable to --privileged, which grants broad privileges.
Why a Docker flag appears to be ignored
Work through these checks in order. Each check isolates a different layer of the deployment.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- Check the allowlist. Compare the option with Coolify’s supported list. An unsupported
docker runargument is not converted into the generated container configuration. - Classify the instruction. Decide whether it changes the image or the running container. Package installation, copied files, users, build stages, and default commands belong in the Dockerfile. Service topology belongs in Compose. Only supported runtime behavior belongs in Custom Docker Options.
- Confirm that the new container started. Saving a value does not necessarily replace the current container. Deploy or restart after changing a container-affecting setting.
- Read deployment and runtime logs. Deployment logs reveal build or command failures; runtime logs reveal entrypoint errors, missing files, permission problems, and application exits. Use both rather than relying on the dashboard’s saved value.
- Check port exposure. For Dockerfile applications, verify that Ports Exposes matches the process’s internal listening port.
- Check the bind address. Confirm the process listens on
0.0.0.0, not only127.0.0.1, so Coolify’s proxy can reach it. - Validate Compose command handling. If a custom build or start command is present, verify that it references the correct Compose file and environment file, with paths relative to Base Directory.
- Check host prerequisites. Devices, GPUs, kernel settings, security profiles, and capabilities depend on the connected server and its Docker runtime. A valid Coolify setting cannot overcome a missing host resource.
Networking, storage, and lifecycle boundaries
Coolify manages networking, storage, domains, health checks, and container lifecycle around the image and runtime options. This is why arbitrary Docker flags are not passed through. A flag that changes port publishing, bind mounts, network attachment, or container replacement behavior could contradict settings Coolify must keep consistent across deployments.
When you need a port, storage mount, environment variable, or resource limit represented in the deployment, prefer the corresponding Coolify control. When you need a service-to-service volume, dependency, health check, or network declaration in a Compose application, define it in Compose. Use the custom field for the allowlisted runtime options that remain after those responsibilities are separated.
Security and reliability considerations
Prefer the narrowest privilege
--privileged, broad capability additions, host devices, and security-option changes can materially expand a container’s access. Start with the smallest capability, device, or limit that satisfies the application. Document why it is required so a later image or application change does not leave unnecessary access enabled.
Treat entrypoint changes as startup changes
Replacing an entrypoint can bypass initialization, migrations, signal handling, or environment preparation that the image author expected. Make sure the replacement executable performs the required setup and keeps the main process in the foreground so health checks and lifecycle events behave predictably.
Keep configuration reproducible
Record the exact Custom Docker Options value with the application’s deployment notes or configuration management. A saved dashboard value is easy to overlook when another person edits the Dockerfile, Compose file, or resource settings. Reproducible documentation should state which layer owns each requirement.
A practical decision checklist
- Is this an image-build instruction? Put it in the Dockerfile.
- Is this a service image, build, command, volume, health check, dependency, environment reference, or network relationship? Put it in Compose when the application uses Compose.
- Is there a dedicated Coolify control for CPU, memory, GPU, ports, storage, or environment variables? Use that control.
- Is it a supported runtime flag such as
--shm-size,--init,--gpus, or--entrypoint? Use General > Custom Docker Options. - Will the change affect the current container? Plan a deploy or restart.
- Does the application need to be reachable through Coolify’s proxy? Expose the correct internal port and bind to
0.0.0.0. - Is the application Compose-based with a custom command? Preserve the correct Compose-file and environment-file handling and keep paths relative to Base Directory.
What a successful change looks like
A successful configuration change has three parts: the option is allowlisted and placed in the correct layer; a deployment or restart creates a container with that configuration; and the application behaves as expected under its normal port, network, and health-check settings. If any part is missing, the dashboard may show a saved value while the running workload remains unchanged or unreachable.
Use deployment logs to confirm that the new revision was built or started, runtime logs to confirm that the process launched with the intended entrypoint and permissions, and an application-level check to confirm the practical result. This verification distinguishes an accepted setting from a working deployment.
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.
