Best Build Workflow for Node and Docker

For node applications, what is the better option for building lightweight images?

Single Docker Image. Might require build tools and would expose all build time environment variables to the container.

yarn install # install deps and devDeps

yarn build # build our application

yarn test # perform tests

yarn install --production --ignore-scripts --prefer-offline # Remove devDeps

rm -rf src # Remove source files

yarn start

Multiple Docker Images

In one docker container that has build tools, do the:
```
yarn install

yarn build

yarn test
```
Then take the build assets and package.json, and copy them into a new container which would have only runtime environment variables. The result is a much smaller image (perhaps node:alpine) that has only very limited source files.
```
yarn install --production --ignore-scripts --prefer-offline

yarn start
```

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

1

If you're aiming for lightweight images, why do you think the first one could ever be better?

– jonrsharpe
Nov 21 '18 at 19:59

I think the second option is better @jonrsharpe for lightweight images as they contain only what is neccessary to run despite the more complicated setup process. But I see so many projects use option 1, and I wonder if there is something I am missing.

– simbolo
Nov 21 '18 at 20:11

1

So did you try either of them? What happened? Maybe other projects aren't aware of the options, or have different goals to yours?

– jonrsharpe
Nov 21 '18 at 20:13

add a comment |

For node applications, what is the better option for building lightweight images?

Single Docker Image. Might require build tools and would expose all build time environment variables to the container.

yarn install # install deps and devDeps

yarn build # build our application

yarn test # perform tests

yarn install --production --ignore-scripts --prefer-offline # Remove devDeps

rm -rf src # Remove source files

yarn start

Multiple Docker Images

In one docker container that has build tools, do the:
```
yarn install

yarn build

yarn test
```
Then take the build assets and package.json, and copy them into a new container which would have only runtime environment variables. The result is a much smaller image (perhaps node:alpine) that has only very limited source files.
```
yarn install --production --ignore-scripts --prefer-offline

yarn start
```

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

1

If you're aiming for lightweight images, why do you think the first one could ever be better?

– jonrsharpe
Nov 21 '18 at 19:59

I think the second option is better @jonrsharpe for lightweight images as they contain only what is neccessary to run despite the more complicated setup process. But I see so many projects use option 1, and I wonder if there is something I am missing.

– simbolo
Nov 21 '18 at 20:11

1

So did you try either of them? What happened? Maybe other projects aren't aware of the options, or have different goals to yours?

– jonrsharpe
Nov 21 '18 at 20:13

add a comment |

For node applications, what is the better option for building lightweight images?

Single Docker Image. Might require build tools and would expose all build time environment variables to the container.

yarn install # install deps and devDeps

yarn build # build our application

yarn test # perform tests

yarn install --production --ignore-scripts --prefer-offline # Remove devDeps

rm -rf src # Remove source files

yarn start

Multiple Docker Images

In one docker container that has build tools, do the:
```
yarn install

yarn build

yarn test
```
Then take the build assets and package.json, and copy them into a new container which would have only runtime environment variables. The result is a much smaller image (perhaps node:alpine) that has only very limited source files.
```
yarn install --production --ignore-scripts --prefer-offline

yarn start
```

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

For node applications, what is the better option for building lightweight images?

Single Docker Image. Might require build tools and would expose all build time environment variables to the container.

yarn install # install deps and devDeps

yarn build # build our application

yarn test # perform tests

yarn install --production --ignore-scripts --prefer-offline # Remove devDeps

rm -rf src # Remove source files

yarn start

Multiple Docker Images

In one docker container that has build tools, do the:
```
yarn install

yarn build

yarn test
```
Then take the build assets and package.json, and copy them into a new container which would have only runtime environment variables. The result is a much smaller image (perhaps node:alpine) that has only very limited source files.
```
yarn install --production --ignore-scripts --prefer-offline

yarn start
```

docker workflow devops

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

edited Nov 21 '18 at 20:06

jonrsharpe

78.6k11110220

asked Nov 21 '18 at 19:52

simbolo

4,33123776

asked Nov 21 '18 at 19:52

simbolo

4,33123776

asked Nov 21 '18 at 19:52

simbolo

4,33123776

1

If you're aiming for lightweight images, why do you think the first one could ever be better?

– jonrsharpe
Nov 21 '18 at 19:59

I think the second option is better @jonrsharpe for lightweight images as they contain only what is neccessary to run despite the more complicated setup process. But I see so many projects use option 1, and I wonder if there is something I am missing.

– simbolo
Nov 21 '18 at 20:11

1

So did you try either of them? What happened? Maybe other projects aren't aware of the options, or have different goals to yours?

– jonrsharpe
Nov 21 '18 at 20:13

add a comment |

1

If you're aiming for lightweight images, why do you think the first one could ever be better?

– jonrsharpe
Nov 21 '18 at 19:59

I think the second option is better @jonrsharpe for lightweight images as they contain only what is neccessary to run despite the more complicated setup process. But I see so many projects use option 1, and I wonder if there is something I am missing.

– simbolo
Nov 21 '18 at 20:11

1

So did you try either of them? What happened? Maybe other projects aren't aware of the options, or have different goals to yours?

– jonrsharpe
Nov 21 '18 at 20:13

If you're aiming for lightweight images, why do you think the first one could ever be better?

– jonrsharpe
Nov 21 '18 at 19:59

I think the second option is better @jonrsharpe for lightweight images as they contain only what is neccessary to run despite the more complicated setup process. But I see so many projects use option 1, and I wonder if there is something I am missing.

– simbolo
Nov 21 '18 at 20:11

So did you try either of them? What happened? Maybe other projects aren't aware of the options, or have different goals to yours?

– jonrsharpe
Nov 21 '18 at 20:13

add a comment |

1 Answer
1

active

oldest

votes

If you want to build lightweight image for your application, keep in mind the following:

Try to use alpine images, e.g. node:8.12.0-alpine as alpine images are lightest base os image. If you want to install packages, do RUN apk add --no-cache --virtual your_packages... && rm -rf /var/cache/apk/*

Try to reduce number of layers by running multiple commands in same RUN statement, e.g. RUN yarn install && yarn build && yarn test && yarn install --production --ignore-scripts --prefer-offline && rm -rf src && yarn start

Try to club commands that cancel out each other, e.g. RUN apk update && apk add ... && rm -rf /var/cache/apk/*. Here apk update creates a cache and rm -rf /var/cache/apk/* clears it. No need to run these two commands separately as they are cancelling out each others work hence no point in having two layers which negate each other and inflate the size of the final image.

Note: Having multiple docker files instead of one is not going to reduce the number of layers or shrink the size. It only gives you logical separation of tasks that you want to handle individually.

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419580%2fbest-build-workflow-for-node-and-docker%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

If you want to build lightweight image for your application, keep in mind the following:

Try to use alpine images, e.g. node:8.12.0-alpine as alpine images are lightest base os image. If you want to install packages, do RUN apk add --no-cache --virtual your_packages... && rm -rf /var/cache/apk/*

Try to reduce number of layers by running multiple commands in same RUN statement, e.g. RUN yarn install && yarn build && yarn test && yarn install --production --ignore-scripts --prefer-offline && rm -rf src && yarn start

Try to club commands that cancel out each other, e.g. RUN apk update && apk add ... && rm -rf /var/cache/apk/*. Here apk update creates a cache and rm -rf /var/cache/apk/* clears it. No need to run these two commands separately as they are cancelling out each others work hence no point in having two layers which negate each other and inflate the size of the final image.

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

add a comment |

If you want to build lightweight image for your application, keep in mind the following:

Try to use alpine images, e.g. node:8.12.0-alpine as alpine images are lightest base os image. If you want to install packages, do RUN apk add --no-cache --virtual your_packages... && rm -rf /var/cache/apk/*

Try to reduce number of layers by running multiple commands in same RUN statement, e.g. RUN yarn install && yarn build && yarn test && yarn install --production --ignore-scripts --prefer-offline && rm -rf src && yarn start

Try to club commands that cancel out each other, e.g. RUN apk update && apk add ... && rm -rf /var/cache/apk/*. Here apk update creates a cache and rm -rf /var/cache/apk/* clears it. No need to run these two commands separately as they are cancelling out each others work hence no point in having two layers which negate each other and inflate the size of the final image.

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

add a comment |

If you want to build lightweight image for your application, keep in mind the following:

Try to use alpine images, e.g. node:8.12.0-alpine as alpine images are lightest base os image. If you want to install packages, do RUN apk add --no-cache --virtual your_packages... && rm -rf /var/cache/apk/*

Try to reduce number of layers by running multiple commands in same RUN statement, e.g. RUN yarn install && yarn build && yarn test && yarn install --production --ignore-scripts --prefer-offline && rm -rf src && yarn start

Try to club commands that cancel out each other, e.g. RUN apk update && apk add ... && rm -rf /var/cache/apk/*. Here apk update creates a cache and rm -rf /var/cache/apk/* clears it. No need to run these two commands separately as they are cancelling out each others work hence no point in having two layers which negate each other and inflate the size of the final image.

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

If you want to build lightweight image for your application, keep in mind the following:

Try to use alpine images, e.g. node:8.12.0-alpine as alpine images are lightest base os image. If you want to install packages, do RUN apk add --no-cache --virtual your_packages... && rm -rf /var/cache/apk/*

Try to reduce number of layers by running multiple commands in same RUN statement, e.g. RUN yarn install && yarn build && yarn test && yarn install --production --ignore-scripts --prefer-offline && rm -rf src && yarn start

Try to club commands that cancel out each other, e.g. RUN apk update && apk add ... && rm -rf /var/cache/apk/*. Here apk update creates a cache and rm -rf /var/cache/apk/* clears it. No need to run these two commands separately as they are cancelling out each others work hence no point in having two layers which negate each other and inflate the size of the final image.

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

edited Nov 22 '18 at 12:47

answered Nov 22 '18 at 12:41

Cyclops

1,03179

answered Nov 22 '18 at 12:41

Cyclops

1,03179

answered Nov 22 '18 at 12:41

Cyclops

1,03179

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

add a comment |

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

Thanks for the insight. I guess it is not practical to to run the build + testing + cleanup commands as a single RUN statement to avoid the extra layer, but more 'cleaner' to run them separately but ultimatly copy them to the final container resulting in just one layer.

– simbolo
Nov 26 '18 at 18:02

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrgtkky