Skip to content
New issue

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

docker-build-step will not forward ports of container, renders plugin useless for starting containers. #34

Open
nfoonf opened this issue Mar 10, 2016 · 2 comments

Comments

@nfoonf
Copy link

nfoonf commented Mar 10, 2016

Actual version of docker build step plugin will under no circumstances forward exposed ports of a container running on Docker Swarm. Neither publishing of all ports nor manual port bindings have any effect on this. As this makes impossible to talk to the started container, it impairs the usefulness of the plugin massively.

Running:
Docker-engine 1.10.2
Docker-Swarm 1.1.3
Jenkins ver. 1.642.2 inside Docker Container with all default config

@nfoonf
Copy link
Author

nfoonf commented Mar 10, 2016

Further investigation of this issue shows that the problem lies in the container/id/start endpoint. this is marked as a Bug in swarm already (docker-archive/classicswarm#1781) .

The plugin configures several variables at the start of an existing container, while these should be most probably configured during creation and only there, to be consistent for example with the 'docker start' command.

@sboschman
Copy link
Contributor

Also created an issue for this on the 'official' Jenkins Jira: https://issues.jenkins-ci.org/browse/JENKINS-33579

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants