Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docker: introduce more layers for smaller images

See original GitHub issue

Expected behaviour

sbt docker:stage could generate a Dockerfile with multiple layers:

one for the OS with JRE
one for the dependencies
one for the resources
one for the code

The idea is to generate layers that do not change frequently and to re-use them. For example, if we change just a line of code, only the last layer has to be pushed.

Actual behaviour

sbt docker:stage generate a Dockerfile with multiple layers:

one for the OS with JRE
one for all the application needs (dependencies, resources, code)

Information

https://phauer.com/2019/no-fat-jar-in-docker-image/

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

muuki88commented, Oct 24, 2019

Related issues and PRS

#368
#723

0reactions

muuki88commented, Feb 26, 2020

Sorry for the late reply 😃

but wanted to implement it from the very beginning (for fun&learn)

those are the best reasons 👍

I’m already building layered images in my daily work and wanted to migrate convention that differs from suggested above

Always happy to have different approaches. I’m not using docker for production at all. So a lot to learn for me as well 😄

I think having more than one option to choose is good for codebase, right?

Definitely 👍 I just wanted to point out all the various efforts as this has been a long standing issue with multiple attempts to fix and it’s a bit messy 😂