Structuring Docker for building a monolithic app
We have a monolithic build process for a ROS-based application, and want to employ Docker to package it up so we can more easily test and deploy.
My current thinking is that I build an image that contains all the dependencies, then use ENTRYPOINT and suitable --mount commands to do our final cmake and build the local source into a container.
However, there is one major design issue I haven't worked out a solution to or best practice for yet. First, I have obtained the OpenCV+CUDA image and a suitable ROS image, so I need to combine both into a new container, but the FROM command doesn't seem to suffice. For instance, OpenCV has been installed with make install, and CUDA has been through whatever apt-get processing is necessary, so I cannot just COPY over the files --from one after switching to the second. Practically, when I currently try to build cmake complains about CUDA_TOOLKIT_ROOT_DIR being missing, and if I hack that there will no doubt be another similar error a few more lines into the makefile.
How do people get around "multiple image inheritance" (for lack of a better word)? Should I be, say, just doing apt get cuda8 in my final Dockerfile instead of relying on FROM docker-opencv-cuda to indirectly provide an environment? That, though has the problem of somehow ensuring my CUDA versions are in sync between images.
docker dockerfile
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
add a comment |
We have a monolithic build process for a ROS-based application, and want to employ Docker to package it up so we can more easily test and deploy.
My current thinking is that I build an image that contains all the dependencies, then use ENTRYPOINT and suitable --mount commands to do our final cmake and build the local source into a container.
However, there is one major design issue I haven't worked out a solution to or best practice for yet. First, I have obtained the OpenCV+CUDA image and a suitable ROS image, so I need to combine both into a new container, but the FROM command doesn't seem to suffice. For instance, OpenCV has been installed with make install, and CUDA has been through whatever apt-get processing is necessary, so I cannot just COPY over the files --from one after switching to the second. Practically, when I currently try to build cmake complains about CUDA_TOOLKIT_ROOT_DIR being missing, and if I hack that there will no doubt be another similar error a few more lines into the makefile.
How do people get around "multiple image inheritance" (for lack of a better word)? Should I be, say, just doing apt get cuda8 in my final Dockerfile instead of relying on FROM docker-opencv-cuda to indirectly provide an environment? That, though has the problem of somehow ensuring my CUDA versions are in sync between images.
docker dockerfile
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
add a comment |
We have a monolithic build process for a ROS-based application, and want to employ Docker to package it up so we can more easily test and deploy.
My current thinking is that I build an image that contains all the dependencies, then use ENTRYPOINT and suitable --mount commands to do our final cmake and build the local source into a container.
However, there is one major design issue I haven't worked out a solution to or best practice for yet. First, I have obtained the OpenCV+CUDA image and a suitable ROS image, so I need to combine both into a new container, but the FROM command doesn't seem to suffice. For instance, OpenCV has been installed with make install, and CUDA has been through whatever apt-get processing is necessary, so I cannot just COPY over the files --from one after switching to the second. Practically, when I currently try to build cmake complains about CUDA_TOOLKIT_ROOT_DIR being missing, and if I hack that there will no doubt be another similar error a few more lines into the makefile.
How do people get around "multiple image inheritance" (for lack of a better word)? Should I be, say, just doing apt get cuda8 in my final Dockerfile instead of relying on FROM docker-opencv-cuda to indirectly provide an environment? That, though has the problem of somehow ensuring my CUDA versions are in sync between images.
docker dockerfile
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
We have a monolithic build process for a ROS-based application, and want to employ Docker to package it up so we can more easily test and deploy.
My current thinking is that I build an image that contains all the dependencies, then use ENTRYPOINT and suitable --mount commands to do our final cmake and build the local source into a container.
However, there is one major design issue I haven't worked out a solution to or best practice for yet. First, I have obtained the OpenCV+CUDA image and a suitable ROS image, so I need to combine both into a new container, but the FROM command doesn't seem to suffice. For instance, OpenCV has been installed with make install, and CUDA has been through whatever apt-get processing is necessary, so I cannot just COPY over the files --from one after switching to the second. Practically, when I currently try to build cmake complains about CUDA_TOOLKIT_ROOT_DIR being missing, and if I hack that there will no doubt be another similar error a few more lines into the makefile.
How do people get around "multiple image inheritance" (for lack of a better word)? Should I be, say, just doing apt get cuda8 in my final Dockerfile instead of relying on FROM docker-opencv-cuda to indirectly provide an environment? That, though has the problem of somehow ensuring my CUDA versions are in sync between images.
docker dockerfile
docker dockerfile
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
asked Nov 16 '18 at 6:04
Ken Y-NKen Y-N
7,838134773
7,838134773
add a comment |
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%2f53332295%2fstructuring-docker-for-building-a-monolithic-app%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%2f53332295%2fstructuring-docker-for-building-a-monolithic-app%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
