Quick and easy way to expose local docker images like a registry?
I am looking to a solution to fasten development with docker images and their testing.
Does it exist a solution that would expose all tagged images from a host through a docker registry API ?
This would allow to do:
- docker build
- List item
- docker tags
- NOT populating a registry
and have the docker image already available, and usable in kubernetes for example.
I am surprise this doesn't already exists.
How do people iterate on docker images (fixing config, checking everything deploy correctly, etc ...) ?
I was used to do it locally with docker-compose, but using Kubernetes makes a registry mandatory and seems to complicate things a bit more.
docker
kubernetes docker-compose docker-registry docker-image asked Jan 3 at 14:43
yvesyves
387717
add a comment |
I am looking to a solution to fasten development with docker images and their testing.
Does it exist a solution that would expose all tagged images from a host through a docker registry API ?
This would allow to do:
- docker build
- List item
- docker tags
- NOT populating a registry
and have the docker image already available, and usable in kubernetes for example.
I am surprise this doesn't already exists.
How do people iterate on docker images (fixing config, checking everything deploy correctly, etc ...) ?
I was used to do it locally with docker-compose, but using Kubernetes makes a registry mandatory and seems to complicate things a bit more.
docker
kubernetes docker-compose docker-registry docker-image asked Jan 3 at 14:43
yvesyves
387717
We have a registry set up, anddocker pusha lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal localdocker runworks).
– David Maze
Jan 3 at 14:50
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27
add a comment |
I am looking to a solution to fasten development with docker images and their testing.
Does it exist a solution that would expose all tagged images from a host through a docker registry API ?
This would allow to do:
- docker build
- List item
- docker tags
- NOT populating a registry
and have the docker image already available, and usable in kubernetes for example.
I am surprise this doesn't already exists.
How do people iterate on docker images (fixing config, checking everything deploy correctly, etc ...) ?
I was used to do it locally with docker-compose, but using Kubernetes makes a registry mandatory and seems to complicate things a bit more.
docker
kubernetes docker-compose docker-registry docker-image asked Jan 3 at 14:43
yvesyves
387717
I am looking to a solution to fasten development with docker images and their testing.
Does it exist a solution that would expose all tagged images from a host through a docker registry API ?
This would allow to do:
- docker build
- List item
- docker tags
- NOT populating a registry
and have the docker image already available, and usable in kubernetes for example.
I am surprise this doesn't already exists.
How do people iterate on docker images (fixing config, checking everything deploy correctly, etc ...) ?
I was used to do it locally with docker-compose, but using Kubernetes makes a registry mandatory and seems to complicate things a bit more.
docker
kubernetes docker-compose docker-registry docker-image docker
kubernetes docker-compose docker-registry docker-image asked Jan 3 at 14:43
yvesyves
387717
asked Jan 3 at 14:43
yvesyves
387717
asked Jan 3 at 14:43
yvesyves
387717
asked Jan 3 at 14:43
yvesyves
387717
asked Jan 3 at 14:43
yvesyves
387717
387717
We have a registry set up, anddocker pusha lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal localdocker runworks).
– David Maze
Jan 3 at 14:50
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27
add a comment |
We have a registry set up, anddocker pusha lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal localdocker runworks).
– David Maze
Jan 3 at 14:50
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27
We have a registry set up, and
docker push a lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal local docker run works).– David Maze
Jan 3 at 14:50
We have a registry set up, and
docker push a lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal local docker run works).– David Maze
Jan 3 at 14:50
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27
add a comment |
0
active
oldest
votes
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%2f54024512%2fquick-and-easy-way-to-expose-local-docker-images-like-a-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f54024512%2fquick-and-easy-way-to-expose-local-docker-images-like-a-registry%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
We have a registry set up, and
docker pusha lot during later phases of development (after the service works locally without Docker, passes its unit tests, and a minimal localdocker runworks).– David Maze
Jan 3 at 14:50
Why do you want to reinvent wheel? Registries are exactly what are you asking for and everybody uses them as they are. Also I would like to recommend building and pushing docker images in the CI so it'ss transparent.
– Azaradel
Jan 3 at 15:54
You're asking for a registry ("docker registry API" what is the main part of a registry) but you don't want a registry. That could be tricky. I think your options are: AWS / Azure (~ $5 per month). Do it yourself: docs.docker.com/registry/deploying/#stop-a-local-registry or artifact servers like nexus.
– Christoph Lütjen
Jan 3 at 16:27