Copy several assets in one layer
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I want to do this:
COPY src/ public/ config-overrides.js /usr/src/app/
But I have learnt the hard way that this actually means:
COPY src/* public/* config-overrides.js /usr/src/app/
Which is not at all what I want.
I can hack this via a .dockerignore, but I do not like that solution because:
- if a new file is added to the repo, it needs to be added to the
.dockerignoretoo. - I like to explicitly list the dependencies in my
Dockerfile
How can I copy an explicit list of files and directories (not just the contents) in a single layer?
Am I simply SOL?
linux docker
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
add a comment |
I want to do this:
COPY src/ public/ config-overrides.js /usr/src/app/
But I have learnt the hard way that this actually means:
COPY src/* public/* config-overrides.js /usr/src/app/
Which is not at all what I want.
I can hack this via a .dockerignore, but I do not like that solution because:
- if a new file is added to the repo, it needs to be added to the
.dockerignoretoo. - I like to explicitly list the dependencies in my
Dockerfile
How can I copy an explicit list of files and directories (not just the contents) in a single layer?
Am I simply SOL?
linux docker
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
add a comment |
I want to do this:
COPY src/ public/ config-overrides.js /usr/src/app/
But I have learnt the hard way that this actually means:
COPY src/* public/* config-overrides.js /usr/src/app/
Which is not at all what I want.
I can hack this via a .dockerignore, but I do not like that solution because:
- if a new file is added to the repo, it needs to be added to the
.dockerignoretoo. - I like to explicitly list the dependencies in my
Dockerfile
How can I copy an explicit list of files and directories (not just the contents) in a single layer?
Am I simply SOL?
linux docker
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
I want to do this:
COPY src/ public/ config-overrides.js /usr/src/app/
But I have learnt the hard way that this actually means:
COPY src/* public/* config-overrides.js /usr/src/app/
Which is not at all what I want.
I can hack this via a .dockerignore, but I do not like that solution because:
- if a new file is added to the repo, it needs to be added to the
.dockerignoretoo. - I like to explicitly list the dependencies in my
Dockerfile
How can I copy an explicit list of files and directories (not just the contents) in a single layer?
Am I simply SOL?
linux docker
linux docker
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
asked Jan 30 at 20:21
dangonfastdangonfast
1,11531429
1,11531429
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can reorganize the repo:
app
+-- src
+-- public
-- config-overrides.js
And then you would just
COPY app/ /usr/src/app/
Another option is to go with a multi-stage build:
FROM scratch as app
COPY src/ /usr/src/app/
COPY public/ /usr/src/app/
COPY config-overrides.js /usr/src/app/
FROM your_base
COPY --from=app /usr/src/app/ /usr/src/app/
Otherwise, keep it 3 separate layers. The added overhead of an additional layer is really minimal. The times you want to merge layers are when you get dozens of layers, if you have the same file in multiple layers and would overwrite it, or you change/delete a file that was created in a previous layer.
answered Jan 31 at 18:31
BMitchBMitch
23717
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1400243%2fcopy-several-assets-in-one-layer%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 can reorganize the repo:
app
+-- src
+-- public
-- config-overrides.js
And then you would just
COPY app/ /usr/src/app/
Another option is to go with a multi-stage build:
FROM scratch as app
COPY src/ /usr/src/app/
COPY public/ /usr/src/app/
COPY config-overrides.js /usr/src/app/
FROM your_base
COPY --from=app /usr/src/app/ /usr/src/app/
Otherwise, keep it 3 separate layers. The added overhead of an additional layer is really minimal. The times you want to merge layers are when you get dozens of layers, if you have the same file in multiple layers and would overwrite it, or you change/delete a file that was created in a previous layer.
answered Jan 31 at 18:31
BMitchBMitch
23717
add a comment |
You can reorganize the repo:
app
+-- src
+-- public
-- config-overrides.js
And then you would just
COPY app/ /usr/src/app/
Another option is to go with a multi-stage build:
FROM scratch as app
COPY src/ /usr/src/app/
COPY public/ /usr/src/app/
COPY config-overrides.js /usr/src/app/
FROM your_base
COPY --from=app /usr/src/app/ /usr/src/app/
Otherwise, keep it 3 separate layers. The added overhead of an additional layer is really minimal. The times you want to merge layers are when you get dozens of layers, if you have the same file in multiple layers and would overwrite it, or you change/delete a file that was created in a previous layer.
answered Jan 31 at 18:31
BMitchBMitch
23717
add a comment |
You can reorganize the repo:
app
+-- src
+-- public
-- config-overrides.js
And then you would just
COPY app/ /usr/src/app/
Another option is to go with a multi-stage build:
FROM scratch as app
COPY src/ /usr/src/app/
COPY public/ /usr/src/app/
COPY config-overrides.js /usr/src/app/
FROM your_base
COPY --from=app /usr/src/app/ /usr/src/app/
Otherwise, keep it 3 separate layers. The added overhead of an additional layer is really minimal. The times you want to merge layers are when you get dozens of layers, if you have the same file in multiple layers and would overwrite it, or you change/delete a file that was created in a previous layer.
answered Jan 31 at 18:31
BMitchBMitch
23717
You can reorganize the repo:
app
+-- src
+-- public
-- config-overrides.js
And then you would just
COPY app/ /usr/src/app/
Another option is to go with a multi-stage build:
FROM scratch as app
COPY src/ /usr/src/app/
COPY public/ /usr/src/app/
COPY config-overrides.js /usr/src/app/
FROM your_base
COPY --from=app /usr/src/app/ /usr/src/app/
Otherwise, keep it 3 separate layers. The added overhead of an additional layer is really minimal. The times you want to merge layers are when you get dozens of layers, if you have the same file in multiple layers and would overwrite it, or you change/delete a file that was created in a previous layer.
answered Jan 31 at 18:31
BMitchBMitch
23717
answered Jan 31 at 18:31
BMitchBMitch
23717
answered Jan 31 at 18:31
BMitchBMitch
23717
answered Jan 31 at 18:31
BMitchBMitch
23717
23717
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1400243%2fcopy-several-assets-in-one-layer%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
