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

Set container hostname #99

Closed
lloydoliver opened this issue Apr 17, 2015 · 3 comments
Closed

Set container hostname #99

lloydoliver opened this issue Apr 17, 2015 · 3 comments

Comments

@lloydoliver
Copy link

I have successfully got the mesos plugin working with our mesos cluster, and it is able to create build slaves just fine. However I am trying to test some Saltstack states which require a hostname to be set for the tests to complete, adding hostname and foobar01 into the parameters of the slave causes docker on mesos to bail out with -

exit status = exited with status 1 stderr = docker: Conflicting options: -h and the network mode (--net). See 'docker run --help'

I've also tried adding a net parameter to the slave with a bridge value, however the plugin seems to have --net host hard coded with no override.
--net host --net=bridge appears in the docker run command.

Also with the hostname, I'd like to be able to use information from the job... for example hostname of foobar-${BUILD_NUMBER}or ${BUILD_TAG} opposed to the hostname of the mesos slave (which breaks the state testing).

Is this already possible, and if so how? If not, is it something that could be added?

@geoffroyjabouley
Copy link
Contributor

Hello

regarding bridged network, there is a pull request #75
it may be included in the next release v0.7

regarding passing parameters to the docker container from the job, i don't think it is possible right now.
Maybe i am wrong, but i guess Jenkins creates new mesos computer/slave before reading the job configuration (except label), so the docker run command can not be override at job level.

@jeschkies
Copy link
Collaborator

jeschkies commented Nov 11, 2019

@lloydoliver, could you try 1.0 or 2.0 of the plugin an see if it works for your case?

@jeschkies
Copy link
Collaborator

Closing for lack of response.

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

3 participants