Hi Maxime,
It is a very valid concern and that's why I've added a patch that should go
out in 0.20.1 to not do a docker pull on every run anymore.
Mesos will still try to docker pull when the image isn't available locally
(via docker inspect), but only once.
The downside ofcourse is that you're
Would it be possible to have a mode where it tries to pull, but then does not
fail solely due to the fail of a pull? In particular, we use tags to indicate
which build should be deployed e.g. “foo-server:production” tag vs
“foo-server:staging” tags.
On Sep 4, 2014, at 11:05 PM, Tim Chen
It is an option that I'm considering adding, but not sure about the failure
to pull part.
Can you create a jira for this? We can then discuss there.
Tim
On Thu, Sep 4, 2014 at 11:19 PM, Steven Schlansker
sschlans...@opentable.com wrote:
Would it be possible to have a mode where it tries to
hi tim,
if it doesn't pull on every run, when will it pull ?
:craig
On 5 Sep 2014, at 07:05, Tim Chen t...@mesosphere.io wrote:
Hi Maxime,
It is a very valid concern and that's why I've added a patch that should go
out in 0.20.1 to not do a docker pull on every run anymore.
Mesos will still
Whilst this is somewhat unrelated to the mesos implementation, I think it
is generally good practice to have immutable tags on the images, this is
something I dislike about docker :)
Whist the gc of old images will eventually become a problem, it will really
only be the layer delta that is
hey ryan,
there are two deployment use-cases i generally have :
- production : i want to consider carefully what i deploy, and refer to
a specific image. a versioned tag works well here
- development : i want to iterate quickly and something like a branch
Hi Ryan,
You can tag each image with your commit hash that way Mesos will always
have to do a docker pull and you don't lose the fast iteration cycle in
development.
Steve
On Friday, September 5, 2014, craig mcmillan mccraigmccr...@gmail.com
wrote:
hey ryan,
there are two deployment
You can tag each image with your commit hash that way Mesos will always
have to do a docker pull and you don't lose the fast iteration cycle in
development.
I mentioned this on one of the review requests the other day. The problem
here is that, say I want to iterate quickly on installing things
Hi,
I'm very new to Mesos and am trying to get a simple Hello World running
with Docker containers.
I've taken a copy of the Java example framework code and have modified it
to launch a docker task.
If I run the mesos slave with the docker containerizer enabled using the
following command then
Hi Javier,
Thanks for the response. I am using mesos 0.20.0 and I have been using
docker for a while on this machine.
I did actually find another email in the mailing list that gave me a
solution for this although I don't fully understand it.
I had to stop mesos and delete all of my previous
The Docker Containerizer will automatically set the $HOME directory for
you, so all you need is to include the .dockercfg as Michael mentioned.
Thanks,
Tim
On Fri, Sep 5, 2014 at 10:32 AM, Michael Babineau
michael.babin...@gmail.com wrote:
You'll need to put a .dockercfg file somewhere the
Hi Tom,
It's definitely a tradeoff between able to automatically pick up latest
changes, and able to have more control of what your cluster is running.
The downside of just pulling latest with the latest is that you might not
know what's exactly running since someone might override latest and
There is some overhead for the JVM itself, which should be added to the
total usage of memory for the task. So you can't have the same amount of
memory for the task as you pass to java, -Xmx parameter.
On 2 September 2014 20:43, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Looks like
Thanks, that was definitely a gotcha!
On Sep 4, 2014, at 4:27 PM, David Greenberg dsg123456...@gmail.com wrote:
Even though command is blank, you must set shell to false. There's a ticket
for this that I don't have off-hand.
On Thursday, September 4, 2014, Steven Schlansker
For those interested, the ticket is
https://issues.apache.org/jira/browse/MESOS-1730
On Fri, Sep 5, 2014 at 4:23 PM, Steven Schlansker sschlans...@opentable.com
wrote:
Thanks, that was definitely a gotcha!
On Sep 4, 2014, at 4:27 PM, David Greenberg dsg123456...@gmail.com
wrote:
Even
15 matches
Mail list logo
