Efficient svn checkout in docker container
I want to checkout some files (specifically, test suite http://llvm.org/svn/llvm-project/test-suite/trunk) in my docker container.
Now I just use RUN svn co http://llvm.org/svn/llvm-project/test-suite/trunk train.out/llvm-test-suite inside Dockerfile.
It works, but doesn't look efficient: on each docker-compose I need to wait for ~5 minutes while the tests are loading.
Is there a better way to prevent Docker from checking out this file each time? The only alternative I see for now is including the file into container.
docker svn docker-compose
asked Nov 12 '18 at 14:08
sooobussooobus
289211
add a comment |
I want to checkout some files (specifically, test suite http://llvm.org/svn/llvm-project/test-suite/trunk) in my docker container.
Now I just use RUN svn co http://llvm.org/svn/llvm-project/test-suite/trunk train.out/llvm-test-suite inside Dockerfile.
It works, but doesn't look efficient: on each docker-compose I need to wait for ~5 minutes while the tests are loading.
Is there a better way to prevent Docker from checking out this file each time? The only alternative I see for now is including the file into container.
docker svn docker-compose
asked Nov 12 '18 at 14:08
sooobussooobus
289211
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat thesvn coeven if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.
– David Maze
Nov 12 '18 at 14:23
add a comment |
I want to checkout some files (specifically, test suite http://llvm.org/svn/llvm-project/test-suite/trunk) in my docker container.
Now I just use RUN svn co http://llvm.org/svn/llvm-project/test-suite/trunk train.out/llvm-test-suite inside Dockerfile.
It works, but doesn't look efficient: on each docker-compose I need to wait for ~5 minutes while the tests are loading.
Is there a better way to prevent Docker from checking out this file each time? The only alternative I see for now is including the file into container.
docker svn docker-compose
asked Nov 12 '18 at 14:08
sooobussooobus
289211
I want to checkout some files (specifically, test suite http://llvm.org/svn/llvm-project/test-suite/trunk) in my docker container.
Now I just use RUN svn co http://llvm.org/svn/llvm-project/test-suite/trunk train.out/llvm-test-suite inside Dockerfile.
It works, but doesn't look efficient: on each docker-compose I need to wait for ~5 minutes while the tests are loading.
Is there a better way to prevent Docker from checking out this file each time? The only alternative I see for now is including the file into container.
docker svn docker-compose
docker svn docker-compose
asked Nov 12 '18 at 14:08
sooobussooobus
289211
asked Nov 12 '18 at 14:08
sooobussooobus
289211
asked Nov 12 '18 at 14:08
sooobussooobus
289211
asked Nov 12 '18 at 14:08
sooobussooobus
289211
asked Nov 12 '18 at 14:08
sooobussooobus
289211
289211
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat thesvn coeven if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.
– David Maze
Nov 12 '18 at 14:23
add a comment |
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat thesvn coeven if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.
– David Maze
Nov 12 '18 at 14:23
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat the
svn co even if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.– David Maze
Nov 12 '18 at 14:23
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat the
svn co even if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.– David Maze
Nov 12 '18 at 14:23
add a comment |
1 Answer
1
active
oldest
votes
You generally don’t run source-control tools from inside a Dockerfile. Check them out in a host directory (better still, if you can manage it, add the Dockerfile directly to the repository you’re trying to build) and run docker build with all of its inputs directly on disk.
There are a couple of good reasons for this:
Docker image caching can often mean that Docker won’t repeat a “clone”, “checkout”, or “pull” type operation: it knows it’s done it once and already knows the output of it and skips the step, even if there are new commits you don’t have.
Adding tools like
svnorgitto the image that you only need to build it makes it unnecessarily larger. (Multi-stage builds can avoid this, but they’re relatively new.)The more common use case for this is to clone a private repository that needs credentials, and it’s hard to avoid leaking those credentials into the final image. (Again multi-stage builds can avoid this, with some care, but it’s better to not have the security exposure at all.)
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
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%2f53263894%2fefficient-svn-checkout-in-docker-container%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
You generally don’t run source-control tools from inside a Dockerfile. Check them out in a host directory (better still, if you can manage it, add the Dockerfile directly to the repository you’re trying to build) and run docker build with all of its inputs directly on disk.
There are a couple of good reasons for this:
Docker image caching can often mean that Docker won’t repeat a “clone”, “checkout”, or “pull” type operation: it knows it’s done it once and already knows the output of it and skips the step, even if there are new commits you don’t have.
Adding tools like
svnorgitto the image that you only need to build it makes it unnecessarily larger. (Multi-stage builds can avoid this, but they’re relatively new.)The more common use case for this is to clone a private repository that needs credentials, and it’s hard to avoid leaking those credentials into the final image. (Again multi-stage builds can avoid this, with some care, but it’s better to not have the security exposure at all.)
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
add a comment |
You generally don’t run source-control tools from inside a Dockerfile. Check them out in a host directory (better still, if you can manage it, add the Dockerfile directly to the repository you’re trying to build) and run docker build with all of its inputs directly on disk.
There are a couple of good reasons for this:
Docker image caching can often mean that Docker won’t repeat a “clone”, “checkout”, or “pull” type operation: it knows it’s done it once and already knows the output of it and skips the step, even if there are new commits you don’t have.
Adding tools like
svnorgitto the image that you only need to build it makes it unnecessarily larger. (Multi-stage builds can avoid this, but they’re relatively new.)The more common use case for this is to clone a private repository that needs credentials, and it’s hard to avoid leaking those credentials into the final image. (Again multi-stage builds can avoid this, with some care, but it’s better to not have the security exposure at all.)
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
add a comment |
You generally don’t run source-control tools from inside a Dockerfile. Check them out in a host directory (better still, if you can manage it, add the Dockerfile directly to the repository you’re trying to build) and run docker build with all of its inputs directly on disk.
There are a couple of good reasons for this:
Docker image caching can often mean that Docker won’t repeat a “clone”, “checkout”, or “pull” type operation: it knows it’s done it once and already knows the output of it and skips the step, even if there are new commits you don’t have.
Adding tools like
svnorgitto the image that you only need to build it makes it unnecessarily larger. (Multi-stage builds can avoid this, but they’re relatively new.)The more common use case for this is to clone a private repository that needs credentials, and it’s hard to avoid leaking those credentials into the final image. (Again multi-stage builds can avoid this, with some care, but it’s better to not have the security exposure at all.)
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
You generally don’t run source-control tools from inside a Dockerfile. Check them out in a host directory (better still, if you can manage it, add the Dockerfile directly to the repository you’re trying to build) and run docker build with all of its inputs directly on disk.
There are a couple of good reasons for this:
Docker image caching can often mean that Docker won’t repeat a “clone”, “checkout”, or “pull” type operation: it knows it’s done it once and already knows the output of it and skips the step, even if there are new commits you don’t have.
Adding tools like
svnorgitto the image that you only need to build it makes it unnecessarily larger. (Multi-stage builds can avoid this, but they’re relatively new.)The more common use case for this is to clone a private repository that needs credentials, and it’s hard to avoid leaking those credentials into the final image. (Again multi-stage builds can avoid this, with some care, but it’s better to not have the security exposure at all.)
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
answered Nov 12 '18 at 14:22
David MazeDavid Maze
11.6k31124
11.6k31124
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%2f53263894%2fefficient-svn-checkout-in-docker-container%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
I know very little about svn, but attaching the checked out project directory as a volume to the container doesn't help?
– lependu
Nov 12 '18 at 14:20
An interesting question is why Docker layer caching isn’t caching this. You often don’t want that (it won’t repeat the
svn coeven if something has changed in the remote repository) but as you’ve described things that should be happening and Docker shouldn’t on its own be repeating this step.– David Maze
Nov 12 '18 at 14:23