You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Docker Compose stack boots up some individual components for stateful and stateless databases, but orchestrates all components of the application within the same container. This so called fat container pattern is discouraged, and each of the jobs could run in individual containers based from the same image, using the command: directive.
Some useful one-off jobs, network routing and dependency control (depends_on:) would have to be in place, for this to work easily. One-time initialisation jobs can always be put into run --rm -it invocations of a container, too.
The text was updated successfully, but these errors were encountered:
Currently the Docker Compose stack boots up some individual components for stateful and stateless databases, but orchestrates all components of the application within the same container. This so called fat container pattern is discouraged, and each of the jobs could run in individual containers based from the same image, using the
command:
directive.Some useful one-off jobs, network routing and dependency control (
depends_on:
) would have to be in place, for this to work easily. One-time initialisation jobs can always be put intorun --rm -it
invocations of a container, too.The text was updated successfully, but these errors were encountered: