The args did the trick
{
…
"args": [
"--application=Test",
"--instance=Test"
]
…
}
Regards
Walter
From: Tim Chen [mailto:[email protected]]
Sent: 11 March 2016 18:41
To: [email protected]
Subject: Re: Mesos 0.27 and docker
Hi Walter,
The parameters field in the container.docker is actually optional parameters
that you can pass to the Docker client when you start the container, not actual
command line arguments for your docker command.
You should specify these in the "command" json value, either part of the value
string or in the args array.
Tim
On Fri, Mar 11, 2016 at 8:56 AM, haosdent
<[email protected]<mailto:[email protected]>> wrote:
Hi, you don't need add "--" before key. Just use "application" and "instance"
should be enough. Mesos would append "--" before parameter key automatically.
On Fri, Mar 11, 2016 at 11:53 PM, Walter Heestermans (TME)
<[email protected]<mailto:[email protected]>>
wrote:
Just a small question I have it up and running for simple HelloWorld , but I
have this docker run command
sudo docker run --rm -i -t --hostname=${HOSTNAME} --volumes-from toyota-apps
--volumes-from toyota-logs -p 8080:8080
toyota/oraclelinux-7-toyota-jdk-8-jetty-9.3:1.0 --application=Test
--jvm-heap-size="-Xms64m -Xmx256m”
These --application=Test --jvm-heap-size="-Xms64m -Xmx256m” are input
arguments to the container, no real docker options
I specified these as
{
…
"container": {
"type": "DOCKER",
"docker": {
…
"parameters": [
{ "key": "--application", "value": "Test" },
{ "key": "--instance", "value": "Test" }
]
},
…
}
These doesn’t seems to be passed to the container. These parameters one is for
real docker command options, or? And is if so, how can I give input arguments
to the container?
Walter
From: Rad Gruchalski [mailto:[email protected]<mailto:[email protected]>]
Sent: 11 March 2016 12:51
To: [email protected]<mailto:[email protected]>
Subject: Re: Mesos 0.27 and docker
I like my life easy so I use Marathon.
Kind regards,
Radek Gruchalski
[email protected]<mailto:[email protected]>
<mailto:[email protected]>
de.linkedin.com/in/radgruchalski/<http://de.linkedin.com/in/radgruchalski/>
Confidentiality:
This communication is intended for the above-named person and may be
confidential and/or legally privileged.
If it has come to you in error you must take no action based on it, nor must
you copy or show it to anyone; please delete/destroy and inform the sender
immediately.
On Friday, 11 March 2016 at 12:24, Walter Heestermans (TME) wrote:
You are specifying two ways, what’s the preferred way?
Walter
From: Rad Gruchalski [mailto:[email protected]]
Sent: 11 March 2016 12:20
To: [email protected]<mailto:[email protected]>
Subject: Re: Mesos 0.27 and docker
Walter,
All you need to know to start is documented here:
https://mesosphere.github.io/marathon/docs/native-docker.html.
That’s with Marathon, if you are planning on using it directly with Mesos,
http://mesos.apache.org/documentation/latest/docker-containerizer/
No problem using latest Docker, I have a 0.27.2 cluster with Docker 1.10.2
(docker-engine). All working perfectly fine.
Kind regards,
Radek Gruchalski
[email protected]<mailto:[email protected]>
<mailto:[email protected]>
de.linkedin.com/in/radgruchalski/<http://de.linkedin.com/in/radgruchalski/>
Confidentiality:
This communication is intended for the above-named person and may be
confidential and/or legally privileged.
If it has come to you in error you must take no action based on it, nor must
you copy or show it to anyone; please delete/destroy and inform the sender
immediately.
On Friday, 11 March 2016 at 11:20, Walter Heestermans (TME) wrote:
Hi,
I’m new using mesos, and I like to make study of the docker containerization
inside mesos.
Can somebody provide me some interesting links and some links to samples on how
to use, configure,…
Walter
This e-mail may contain confidential information. If you are not an addressee
or otherwise authorised to receive this message, you should not use, copy,
disclose or take any action based on this e-mail. If you have received this
e-mail in error, please inform the sender promptly and delete this message and
any attachments immediately.
This e-mail may contain confidential information. If you are not an addressee
or otherwise authorised to receive this message, you should not use, copy,
disclose or take any action based on this e-mail. If you have received this
e-mail in error, please inform the sender promptly and delete this message and
any attachments immediately.
This e-mail may contain confidential information. If you are not an addressee
or otherwise authorised to receive this message, you should not use, copy,
disclose or take any action based on this e-mail. If you have received this
e-mail in error, please inform the sender promptly and delete this message and
any attachments immediately.
--
Best Regards,
Haosdent Huang
This e-mail may contain confidential information. If you are not an addressee
or otherwise authorised to receive this message, you should not use, copy,
disclose or take any action based on this e-mail. If you have received this
e-mail in error, please inform the sender promptly and delete this message and
any attachments immediately.
