How to stop docker-machine create from pruning images
Is there a way to disable docker-machine from deleting docker images when creating host instances?
My team is using Gitlab's gitlab-runner autoscaling with docker-machine for CI on AWS. We're emulating gitlab.com's functionality where each build gets a fresh EC2 instance with docker running.
To help speed up builds I've created a custom AMI where common docker images are pulled locally. Docker-machine uses this AMI to create EC2 instances. Unfortunately the docker-machine create startup deletes all local images on the AMI.
amazon-web-services docker gitlab docker-machine gitlab-ci-runner
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
add a comment |
Is there a way to disable docker-machine from deleting docker images when creating host instances?
My team is using Gitlab's gitlab-runner autoscaling with docker-machine for CI on AWS. We're emulating gitlab.com's functionality where each build gets a fresh EC2 instance with docker running.
To help speed up builds I've created a custom AMI where common docker images are pulled locally. Docker-machine uses this AMI to create EC2 instances. Unfortunately the docker-machine create startup deletes all local images on the AMI.
amazon-web-services docker gitlab docker-machine gitlab-ci-runner
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
add a comment |
Is there a way to disable docker-machine from deleting docker images when creating host instances?
My team is using Gitlab's gitlab-runner autoscaling with docker-machine for CI on AWS. We're emulating gitlab.com's functionality where each build gets a fresh EC2 instance with docker running.
To help speed up builds I've created a custom AMI where common docker images are pulled locally. Docker-machine uses this AMI to create EC2 instances. Unfortunately the docker-machine create startup deletes all local images on the AMI.
amazon-web-services docker gitlab docker-machine gitlab-ci-runner
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
Is there a way to disable docker-machine from deleting docker images when creating host instances?
My team is using Gitlab's gitlab-runner autoscaling with docker-machine for CI on AWS. We're emulating gitlab.com's functionality where each build gets a fresh EC2 instance with docker running.
To help speed up builds I've created a custom AMI where common docker images are pulled locally. Docker-machine uses this AMI to create EC2 instances. Unfortunately the docker-machine create startup deletes all local images on the AMI.
amazon-web-services docker gitlab docker-machine gitlab-ci-runner
amazon-web-services docker gitlab docker-machine gitlab-ci-runner
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
asked Nov 22 at 18:22
Ian Dunbar-Hall
31
31
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I'm not aware of a way to customize Docker Machine's provisioners directly. In short, Docker Machine has provisioners for each OS type that controls what it does to set up Docker. You can see the different provisioners in /libmachine/provision in the repo.
You might be able to get what you want if you base your custom AMI on something like CoreOS. Its provisioner just uses the Docker that's pre-installed, so I think it should leave your pre-pulled images alone.
answered Nov 22 at 19:31
King Chung Huang
1,13089
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436419%2fhow-to-stop-docker-machine-create-from-pruning-images%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'm not aware of a way to customize Docker Machine's provisioners directly. In short, Docker Machine has provisioners for each OS type that controls what it does to set up Docker. You can see the different provisioners in /libmachine/provision in the repo.
You might be able to get what you want if you base your custom AMI on something like CoreOS. Its provisioner just uses the Docker that's pre-installed, so I think it should leave your pre-pulled images alone.
answered Nov 22 at 19:31
King Chung Huang
1,13089
add a comment |
I'm not aware of a way to customize Docker Machine's provisioners directly. In short, Docker Machine has provisioners for each OS type that controls what it does to set up Docker. You can see the different provisioners in /libmachine/provision in the repo.
You might be able to get what you want if you base your custom AMI on something like CoreOS. Its provisioner just uses the Docker that's pre-installed, so I think it should leave your pre-pulled images alone.
answered Nov 22 at 19:31
King Chung Huang
1,13089
add a comment |
I'm not aware of a way to customize Docker Machine's provisioners directly. In short, Docker Machine has provisioners for each OS type that controls what it does to set up Docker. You can see the different provisioners in /libmachine/provision in the repo.
You might be able to get what you want if you base your custom AMI on something like CoreOS. Its provisioner just uses the Docker that's pre-installed, so I think it should leave your pre-pulled images alone.
answered Nov 22 at 19:31
King Chung Huang
1,13089
I'm not aware of a way to customize Docker Machine's provisioners directly. In short, Docker Machine has provisioners for each OS type that controls what it does to set up Docker. You can see the different provisioners in /libmachine/provision in the repo.
You might be able to get what you want if you base your custom AMI on something like CoreOS. Its provisioner just uses the Docker that's pre-installed, so I think it should leave your pre-pulled images alone.
answered Nov 22 at 19:31
King Chung Huang
1,13089
answered Nov 22 at 19:31
King Chung Huang
1,13089
answered Nov 22 at 19:31
King Chung Huang
1,13089
answered Nov 22 at 19:31
King Chung Huang
1,13089
1,13089
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436419%2fhow-to-stop-docker-machine-create-from-pruning-images%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
