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
The top-level docker deploy command (using the "Docker Application Bundle" (.dab) file format was introduced as an experimental feature in Docker 1.13 / 17.03, but superseded by support for Docker Compose files (and docker app / CNAB).
With no development being done on this feature, and no active use of the file format, we will be removing support for the DAB file format, and the top-level docker deploy command (hidden by default in 19.03 through #1602), in favour of docker stack deploy using compose files.
thaJeztah
changed the title
[epic] remove experimental "docker (stack) deploy" from "dab" files
[epic] remove experimental "docker (stack) deploy" using "dab" files
Dec 6, 2019
No, I think we're all set: we updated the documentation already (even though it's not "removed" yet from the current release, but doesn't hurt to limit exposure of the feature).
The top-level
docker deploy
command (using the "Docker Application Bundle" (.dab
) file format was introduced as an experimental feature in Docker 1.13 / 17.03, but superseded by support for Docker Compose files (anddocker app
/ CNAB).With no development being done on this feature, and no active use of the file format, we will be removing support for the DAB file format, and the top-level
docker deploy
command (hidden by default in 19.03 through #1602), in favour ofdocker stack deploy
using compose files.docker deploy
command (Remove experimental "deploy" from "dab" files #2216)--bundle-file
flags from commands (Remove experimental "deploy" from "dab" files #2216)docker-compose bundle
command (used to convert docker-compose files to.dab
) (Remove "bundle" subcommand and support for DAB files compose#7085).dab
format anddocker deploy
subcommand (Remove "bundle" subcommand and support for DAB files docs#9987).The text was updated successfully, but these errors were encountered: