Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Use exec-form ENTRYPOINT for the executable that defines your container’s job, and use exec-form CMD for default arguments that users may replace. A typical image therefore looks like this:

FROM alpine:3.20
COPY entrypoint.sh /usr/local/bin/entrypoint.sh
RUN chmod +x /usr/local/bin/entrypoint.sh
ENTRYPOINT ["/usr/local/bin/entrypoint.sh"]
CMD ["--help"]

When no setup wrapper is needed, point ENTRYPOINT directly at the application:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
FROM python:3.13-slim
WORKDIR /app
COPY . .
ENTRYPOINT ["python", "-m", "myapp"]
CMD ["--config", "/etc/myapp/config.yml"]

This arrangement gives the image a stable executable while retaining a clean way to provide alternate arguments at runtime. It also normally makes the application process PID 1, which is important for receiving Docker’s stop signal and shutting down gracefully.

What ENTRYPOINT does

Docker’s ENTRYPOINT instruction configures a container to run as an executable. It expresses the image’s primary job: an image with an entrypoint behaves like the program named by that instruction rather than like a generic operating-system shell.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.

Docker supports two syntaxes:

Form Syntax How Docker starts it Best fit
Exec form ENTRYPOINT ["executable", "param1", "param2"] Runs the executable directly from a JSON array. Most applications and reusable images.
Shell form ENTRYPOINT command param1 param2 Passes the command through the image’s shell, normally /bin/sh -c on Linux. Commands that intentionally require shell parsing.

There must be at least one runnable CMD or ENTRYPOINT command in an image. In practice, an executable image commonly uses both instructions: ENTRYPOINT identifies the program, and CMD supplies its defaults.

Start with the executable role

Decide first what the container is supposed to be. If the image exists to run a Python module, make the interpreter and module the entrypoint. If the image needs initialization before launching the application, make an executable wrapper script the entrypoint and have that script hand control to the application.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Direct application entrypoint

For a Python module, split the executable and each argument into separate JSON elements:

ENTRYPOINT ["python", "-m", "myapp"]

Docker starts python directly, passes -m and myapp as arguments, and keeps the command’s argument boundaries unambiguous. This is different from placing the entire command in one element.

Wrapper-script entrypoint

A wrapper is useful when the image must perform setup such as preparing directories or validating environment state before starting the application:

FROM alpine:3.20
COPY entrypoint.sh /usr/local/bin/entrypoint.sh
RUN chmod +x /usr/local/bin/entrypoint.sh
ENTRYPOINT ["/usr/local/bin/entrypoint.sh"]
CMD ["--help"]

The RUN chmod +x line makes the copied script executable. Adapt the path and permission step to the selected base image, but keep the entrypoint in exec form unless shell interpretation is an intentional requirement.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How Docker combines ENTRYPOINT and CMD

Think of the final launch as two parts: a fixed executable portion and an argument portion. The exec-form ENTRYPOINT supplies the fixed portion. The exec-form CMD supplies argument defaults when the caller gives none. If the caller writes arguments after the image name, those runtime arguments replace the CMD array; they do not append to it.

For example:

ENTRYPOINT ["top", "-b"]
CMD ["-c"]

Running docker run image uses the entrypoint and its default argument, equivalent to top -b -c. Running docker run image -H keeps top -b but substitutes -H for -c. This is why options that users are expected to change belong in CMD, while the identity of the program belongs in ENTRYPOINT.

Do not expect a positional runtime argument to replace the executable. To replace the executable itself, use --entrypoint. Keeping these two override mechanisms separate makes an image predictable for both automated jobs and interactive troubleshooting.

Why an explicit CMD matters after adding ENTRYPOINT

If the base image supplied a CMD, adding an ENTRYPOINT in your Dockerfile can reset that inherited default. Define the desired CMD again in the current Dockerfile instead of assuming the parent image’s arguments will remain available.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Only the final ENTRYPOINT instruction has an effect. Multiple entrypoint lines do not create a sequence of programs; later instructions replace earlier ones. Keep one deliberate entrypoint in the final image and pair it with the command defaults you actually want.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

ENTRYPOINT and CMD: the intended pairing

The most useful mental model is that ENTRYPOINT is stable and CMD is replaceable. With an exec-form entrypoint, Docker appends arguments supplied after the image name to the entrypoint and uses them instead of the CMD defaults.

ENTRYPOINT ["top", "-b"]
CMD ["-c"]

Starting the image without extra arguments produces the equivalent of top -b -c. Supplying a different argument list replaces the default command arguments while preserving the entrypoint:

docker run --rm image -H

That invocation retains top -b and passes -H as the runtime argument. This pattern is appropriate when callers should be able to select configuration files, modes, or flags without changing the program the image runs.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Exec form versus shell form

The syntax choice changes argument handling, shell features, and process behavior.

Question Exec-form ENTRYPOINT Shell-form ENTRYPOINT
Does Docker invoke a shell automatically? No. The first JSON element is executed directly. Yes. The command is interpreted by the image’s shell.
Can CMD defaults be used as replaceable arguments? Yes, when the entrypoint is paired with exec-form CMD. No. Shell-form ENTRYPOINT ignores CMD and positional arguments supplied to docker run.
Are pipes, redirection, chaining, and expansion available? Not automatically. Invoke a shell explicitly if those features are intentional. Yes, because the shell parses the command.
Who normally receives Docker’s stop signal? The application normally becomes PID 1. The shell can remain between Docker and the application, so the application may not receive the signal directly.
Recommended default Preferred for predictable argument passing and signal handling. Use only when shell behavior is part of the design.

When shell behavior is genuinely required

Exec form does not expand variables, connect pipelines, perform redirection, or process command chaining. If the application really needs those shell features, invoke the shell explicitly rather than assuming Docker will provide it:

ENTRYPOINT ["/bin/sh", "-c", "exec myapp "$@"", "--"]

Here the shell is an explicit part of the entrypoint. The exec in the command string replaces the shell with myapp after parsing, preserving the desired process behavior while retaining shell syntax. Use this pattern only when that parsing is required; otherwise, call the application directly in exec form.

PID 1 and graceful shutdown

Docker sends a container’s stop signal to its main process. With an exec-form entrypoint, the application normally becomes PID 1, so it can receive the signal and perform its own graceful shutdown.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A shell-form entrypoint can leave the shell as the main process. In that arrangement, the shell may receive the signal while the application continues running or fails to perform its normal cleanup. This is a common reason an application appears not to stop correctly.

Docker’s build check named JSONArgsRecommended recommends JSON-array CMD and ENTRYPOINT for this signal-handling reason. Treat a warning from that check as a prompt to examine whether a shell is being inserted unnecessarily.

The required wrapper-script hand-off

If setup code requires a script, finish the script by replacing itself with the final command:

#!/bin/sh
set -eu
# optional setup here
exec "$@"

The shell script remains responsible for the optional setup, but exec "$@" replaces the script process with the application. The application then occupies PID 1 instead of remaining a child hidden behind the wrapper.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.

Writing a reliable entrypoint script

  1. Choose a base image that contains the interpreter you need. A script beginning with #!/bin/sh requires a compatible shell in the image.
  2. Copy the script into a known executable path. For example, copy it to /usr/local/bin/entrypoint.sh.
  3. Set execute permission during the build. Use a RUN chmod +x step or an equivalent file-permission method supported by the build.
  4. Perform only the setup the image needs. Keep the wrapper’s responsibilities clear so that runtime arguments can still be passed to the application.
  5. End with exec "$@". This hand-off makes the final application the container’s main process.
  6. Declare the script with exec-form ENTRYPOINT. Keep default application flags in a separate exec-form CMD.

A wrapper should not silently discard arguments. If the image is started with a replacement argument list, those values should reach the final application through the script’s positional parameters.

Keep setup and application arguments separate

Initialization belongs before the hand-off; application options belong after it. Avoid baking mutable flags into the wrapper when they are intended to be changed by callers. Put those defaults in CMD so a command such as docker run --rm myimage --config /tmp/test.yml can replace them without editing the image.

Likewise, do not add a second entrypoint merely to perform another setup phase. Combine the required setup in one script, then use one final exec. Since only the last ENTRYPOINT instruction is effective, multiple instructions cannot form a chain.

Overriding commands at runtime

Replace CMD defaults

Put ordinary arguments after the image name when you want a different argument list but the same executable:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
docker run --rm myimage --config /tmp/test.yml

With an exec-form ENTRYPOINT, this replaces the image’s CMD defaults and passes --config /tmp/test.yml to the configured entrypoint.

Replace ENTRYPOINT itself

Use --entrypoint when you need to replace the configured executable:

docker run --rm --entrypoint /bin/sh -it myimage

This is useful for diagnosing startup failures, checking whether files were copied to the expected locations, or launching a one-off maintenance command. It bypasses the image’s normal entrypoint rather than merely changing its arguments.

Choosing the right override

Goal Command form Result
Keep the image executable, change its arguments docker run image new-arguments Replaces CMD defaults while retaining ENTRYPOINT.
Launch a different executable docker run --entrypoint /path/to/program image Replaces ENTRYPOINT.
Inspect a failing image interactively docker run --rm --entrypoint /bin/sh -it image Starts a shell instead of the normal application.

Common ENTRYPOINT mistakes and fixes

Putting a whole command in one JSON element

This instruction asks Docker to find one executable whose name contains spaces:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
ENTRYPOINT ["python -m myapp"]

Split the executable and its arguments into separate elements:

ENTRYPOINT ["python", "-m", "myapp"]

Using single quotes in exec form

Exec form is JSON array syntax, and JSON requires double quotes. Use "python", not 'python', for each array element. If you need shell quoting rules, invoke the shell deliberately rather than mixing shell notation into a JSON array.

Expecting shell expansion from exec form

An instruction such as ENTRYPOINT ["myapp", "$CONFIG"] does not automatically expand $CONFIG; no shell is involved. Pass the value through the application’s own configuration mechanism or invoke a shell explicitly when expansion is part of the requirement.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

Using shell form when arguments must be overridable

Shell-form ENTRYPOINT ignores CMD and positional arguments supplied to docker run. If users need to replace default flags, change the entrypoint to exec form and place defaults in CMD.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Leaving out exec in a wrapper

A wrapper that ends after launching the application remains PID 1 and may absorb stop signals. Finish it with exec "$@" so the application replaces the wrapper process.

Relying on an inherited CMD

Adding an entrypoint can clear a base image’s command defaults. Define an explicit CMD in your Dockerfile whenever the image depends on particular default arguments.

Defining several ENTRYPOINT instructions

Only the last entrypoint is effective. Remove obsolete lines or ensure the final instruction is the one that describes the image’s actual executable role.

Choosing a pattern for your image

Use a direct exec-form entrypoint when the image has one clear application and needs no initialization. This is the smallest and easiest-to-debug design: Docker starts the application directly, callers can replace its default arguments, and the application normally receives the stop signal as PID 1.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use an exec-form script entrypoint when setup is genuinely required, such as preparing directories or validating runtime state. The script adds an implementation requirement—the interpreter must exist, the file must be executable, and the final line must hand off with exec—but it preserves the same runtime override model when it forwards "$@".

Use an explicit shell entrypoint only when pipes, redirection, expansion, or command chaining are part of the container’s intended behavior. This choice makes shell parsing visible, but it gives up the convenient CMD-and-positional-argument replacement behavior and can complicate signal delivery. A shell dependency should therefore be a conscious design decision rather than a shortcut for writing a command on one line.

Design question Direct exec form Wrapper exec form Explicit shell form
Stable executable Application itself Wrapper, then application Shell command
Replaceable defaults Yes, through CMD Yes, if arguments are forwarded No, positional arguments and CMD are ignored
Shell syntax Only with an explicit shell Only inside intentional setup or an explicit shell Available by definition
Shutdown behavior Application normally receives the signal Application receives it after exec Shell may remain between Docker and application
Extra requirements Executable path and arguments must be correct Interpreter, copy step, permissions, and hand-off Compatible shell and carefully quoted command
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A practical design checklist

  • Is the image’s primary executable clearly identified?
  • Is ENTRYPOINT written in JSON-array exec form?
  • Are the executable and every argument separate array elements?
  • Are default, user-replaceable flags in an exec-form CMD?
  • Does the design intentionally require shell pipes, redirection, expansion, or chaining?
  • If a shell is required, is it invoked explicitly?
  • If a wrapper script is used, is it executable in the image?
  • Does the wrapper end with exec "$@"?
  • Has the Dockerfile restored an explicit CMD after adding ENTRYPOINT?
  • Can you use ordinary runtime arguments to change defaults and --entrypoint to debug the executable itself?

Putting the patterns together

For a reusable application image, the clearest pattern is:

ENTRYPOINT ["application"]
CMD ["--default-flag"]

For an application that needs setup:

ENTRYPOINT ["/usr/local/bin/entrypoint.sh"]
CMD ["--default-flag"]

For a command that intentionally depends on shell parsing, make that dependency visible:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
ENTRYPOINT ["/bin/sh", "-c", "exec myapp "$@"", "--"]

The first two patterns provide predictable argument replacement and direct signal delivery. The third trades some of that simplicity for explicit shell behavior, so it should be reserved for cases where shell syntax is actually needed.

Final guidance

Think of ENTRYPOINT as the image’s executable identity, not as a general-purpose place to write an entire shell command. Use exec form by default, keep replaceable defaults in CMD, and use positional docker run arguments when changing those defaults. When setup requires a script, make the script executable and end it with an exec hand-off. Reserve shell form for deliberate shell parsing, and use --entrypoint when debugging or replacing the executable itself.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

Frequently Asked Questions

What does ENTRYPOINT do in a Dockerfile?

It configures the executable a container runs. In exec form, Docker starts the named program directly, making it the image’s stable executable role.

What is the difference between ENTRYPOINT and CMD?

Use ENTRYPOINT for the executable identity and CMD for default arguments. Runtime arguments after the image name replace CMD defaults while retaining an exec-form ENTRYPOINT.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Should I use exec form or shell form?

Use exec form by default. It gives predictable argument boundaries and normally makes the application PID 1. Choose shell form only when shell parsing such as pipelines, redirection, chaining, or expansion is intentional.

Why does docker stop not stop my application cleanly?

A shell-form entrypoint or a wrapper without exec can remain PID 1 and receive Docker’s stop signal instead of the application. Use exec-form ENTRYPOINT, or end a required wrapper with exec "$@".

How do I override an ENTRYPOINT?

Pass --entrypoint to docker run, for example docker run --rm --entrypoint /bin/sh -it myimage. This replaces the executable rather than merely changing its arguments.

How do I change only the default arguments?

Put ordinary arguments after the image name, such as docker run --rm myimage --config /tmp/test.yml. With exec-form ENTRYPOINT, these replace CMD defaults.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Why does ENTRYPOINT ["python -m myapp"] fail?

The JSON array contains one executable name with spaces. Docker does not split it through a shell. Write ENTRYPOINT ["python", "-m", "myapp"] instead.

Why did my base image’s CMD disappear?

Defining ENTRYPOINT can reset an inherited CMD. Add the desired CMD explicitly in the current Dockerfile, and remember that only the last ENTRYPOINT instruction is effective.

Can exec-form ENTRYPOINT expand environment variables?

No. Exec form does not invoke a shell, so values such as $CONFIG are not expanded automatically. Use the application’s configuration handling or invoke a shell explicitly when expansion is required.

The Bottom Line

Use exec-form ENTRYPOINT for the program your image is meant to run, pair it with exec-form CMD for replaceable defaults, and use --entrypoint only when replacing the executable itself. If a wrapper is necessary, make it executable and finish with exec "$@" so the real application remains PID 1. Reserve shell form for deliberate shell parsing.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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.