what should be the max allowed image size for micro services on kubernetes
Some times I observe Imagepullbackoff or Imagepullerror in kubernets deployment.
Is there any restriction for docker image size on kubernets for pulling image.
Thanks
docker
kubernetes asked Nov 28 '18 at 0:09
KhumarKhumar
469
add a comment |
Some times I observe Imagepullbackoff or Imagepullerror in kubernets deployment.
Is there any restriction for docker image size on kubernets for pulling image.
Thanks
docker
kubernetes asked Nov 28 '18 at 0:09
KhumarKhumar
469
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20
add a comment |
Some times I observe Imagepullbackoff or Imagepullerror in kubernets deployment.
Is there any restriction for docker image size on kubernets for pulling image.
Thanks
docker
kubernetes asked Nov 28 '18 at 0:09
KhumarKhumar
469
Some times I observe Imagepullbackoff or Imagepullerror in kubernets deployment.
Is there any restriction for docker image size on kubernets for pulling image.
Thanks
docker
kubernetes docker
kubernetes asked Nov 28 '18 at 0:09
KhumarKhumar
469
asked Nov 28 '18 at 0:09
KhumarKhumar
469
asked Nov 28 '18 at 0:09
KhumarKhumar
469
asked Nov 28 '18 at 0:09
KhumarKhumar
469
asked Nov 28 '18 at 0:09
KhumarKhumar
469
469
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20
add a comment |
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20
add a comment |
1 Answer
1
active
oldest
votes
It's straightforward to get a ~1 GB image (anything that apt-get install build-essential will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.
In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range. These have generally manifested as problems with docker push and docker pull being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.
As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.
(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range. A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
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%2f53510163%2fwhat-should-be-the-max-allowed-image-size-for-micro-services-on-kubernetes%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
It's straightforward to get a ~1 GB image (anything that apt-get install build-essential will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.
In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range. These have generally manifested as problems with docker push and docker pull being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.
As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.
(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range. A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
add a comment |
It's straightforward to get a ~1 GB image (anything that apt-get install build-essential will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.
In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range. These have generally manifested as problems with docker push and docker pull being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.
As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.
(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range. A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
add a comment |
It's straightforward to get a ~1 GB image (anything that apt-get install build-essential will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.
In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range. These have generally manifested as problems with docker push and docker pull being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.
As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.
(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range. A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
It's straightforward to get a ~1 GB image (anything that apt-get install build-essential will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.
In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range. These have generally manifested as problems with docker push and docker pull being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.
As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.
(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range. A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
answered Nov 28 '18 at 1:46
David MazeDavid Maze
15.1k31429
15.1k31429
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.
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%2f53510163%2fwhat-should-be-the-max-allowed-image-size-for-micro-services-on-kubernetes%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
imagesize should be small , but it doesnt mean that there is some restriction , untill you exaust ur storage
– Ijaz Ahmad Khan
Nov 28 '18 at 0:20