We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to deploy a stack with Docker 17.06.2-ce
A service is having 'init:' property set:
version: "3.1" services: dummy: image: hello-world init: true
Getting an error:
$ docker stack deploy -c dummy.yml dummy init Additional property init is not allowed
The 'init:' option had been introduced in version 2.2 of 'docker-compose' format. Any clue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Is the init: option supported by docker stack deploy? Does your example file work with docker-compose?
init:
docker stack deploy
docker-compose
I found init: listed under https://docs.docker.com/compose/compose-file/compose-file-v2/#init (in the 2.2 file format reference), but not under the v3 reference, so perhaps it was removed in v3? (likely due to not being supported for services under Swarm Mode -- see moby/moby#25303, where it appears moby/swarmkit#2350 was merged in swarmkit, but still pending for CLI in docker/cli#51 and/or moby/moby#34529)
2.2
Sorry, something went wrong.
Additionally, in the future, it'd be better to post questions like this in the Docker Community Forums, the Docker Community Slack, or on Stack Overflow. Thanks!
Compose file support was implemented in docker/cli#1129, and completes a long chain of PR's to implement this feature 🎉
No branches or pull requests
Trying to deploy a stack with Docker 17.06.2-ce
A service is having 'init:' property set:
Getting an error:
The 'init:' option had been introduced in version 2.2 of 'docker-compose' format. Any clue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: