Docker: speed up SBT image. (Getting org.scala-sbt sbt 1.2.6 (this may take some time)…)
I use hseeberger/scala-sbt Docker image.
When I run this image like:
docker run -it
-v `pwd`:/root
hseeberger/scala-sbt sbt test
It takes a long time for this:
Getting org.scala-sbt sbt 1.2.6 (this may take some time)...
What I don't understand is that this image already defines that the SBT-Version is 1.2.6 as well as my project does?
docker sbt
add a comment |
I use hseeberger/scala-sbt Docker image.
When I run this image like:
docker run -it
-v `pwd`:/root
hseeberger/scala-sbt sbt test
It takes a long time for this:
Getting org.scala-sbt sbt 1.2.6 (this may take some time)...
What I don't understand is that this image already defines that the SBT-Version is 1.2.6 as well as my project does?
docker sbt
Without having a closer look.docker diff
might give you a hint what is going on.
– TobiSH
Nov 15 '18 at 13:24
add a comment |
I use hseeberger/scala-sbt Docker image.
When I run this image like:
docker run -it
-v `pwd`:/root
hseeberger/scala-sbt sbt test
It takes a long time for this:
Getting org.scala-sbt sbt 1.2.6 (this may take some time)...
What I don't understand is that this image already defines that the SBT-Version is 1.2.6 as well as my project does?
docker sbt
I use hseeberger/scala-sbt Docker image.
When I run this image like:
docker run -it
-v `pwd`:/root
hseeberger/scala-sbt sbt test
It takes a long time for this:
Getting org.scala-sbt sbt 1.2.6 (this may take some time)...
What I don't understand is that this image already defines that the SBT-Version is 1.2.6 as well as my project does?
docker sbt
docker sbt
asked Nov 15 '18 at 11:28
pmepme
2,77311427
2,77311427
Without having a closer look.docker diff
might give you a hint what is going on.
– TobiSH
Nov 15 '18 at 13:24
add a comment |
Without having a closer look.docker diff
might give you a hint what is going on.
– TobiSH
Nov 15 '18 at 13:24
Without having a closer look.
docker diff
might give you a hint what is going on.– TobiSH
Nov 15 '18 at 13:24
Without having a closer look.
docker diff
might give you a hint what is going on.– TobiSH
Nov 15 '18 at 13:24
add a comment |
2 Answers
2
active
oldest
votes
It's probably because you sbt
is being lazy, and will actually download some of the jars only when it needs them (when sbt is first run).
If you want to speed it up. You can use this image as a base image in your Dockerfile (FROM hseeberger/scala-sbt
) and run sbt test
once without a test project, so it download the JARs.
add a comment |
If you wanna stick on sbt 1.2.6 you can just use the latest version hseeberger/scala-sbt
which is 11.0.1_2.12.7_1.2.6
.
docker pull hseeberger/scala-sbt:11.0.1_2.12.7_1.2.6
The version number contains of the openjdk version (11.0.1), the scala version (2.12.7) and the sbt version (1.2.6). If that's all you need there is no need to reinvent the wheel :-D
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
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%2f53318465%2fdocker-speed-up-sbt-image-getting-org-scala-sbt-sbt-1-2-6-this-may-take-some%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's probably because you sbt
is being lazy, and will actually download some of the jars only when it needs them (when sbt is first run).
If you want to speed it up. You can use this image as a base image in your Dockerfile (FROM hseeberger/scala-sbt
) and run sbt test
once without a test project, so it download the JARs.
add a comment |
It's probably because you sbt
is being lazy, and will actually download some of the jars only when it needs them (when sbt is first run).
If you want to speed it up. You can use this image as a base image in your Dockerfile (FROM hseeberger/scala-sbt
) and run sbt test
once without a test project, so it download the JARs.
add a comment |
It's probably because you sbt
is being lazy, and will actually download some of the jars only when it needs them (when sbt is first run).
If you want to speed it up. You can use this image as a base image in your Dockerfile (FROM hseeberger/scala-sbt
) and run sbt test
once without a test project, so it download the JARs.
It's probably because you sbt
is being lazy, and will actually download some of the jars only when it needs them (when sbt is first run).
If you want to speed it up. You can use this image as a base image in your Dockerfile (FROM hseeberger/scala-sbt
) and run sbt test
once without a test project, so it download the JARs.
answered Nov 15 '18 at 14:44
Uku LoskitUku Loskit
30.7k86980
30.7k86980
add a comment |
add a comment |
If you wanna stick on sbt 1.2.6 you can just use the latest version hseeberger/scala-sbt
which is 11.0.1_2.12.7_1.2.6
.
docker pull hseeberger/scala-sbt:11.0.1_2.12.7_1.2.6
The version number contains of the openjdk version (11.0.1), the scala version (2.12.7) and the sbt version (1.2.6). If that's all you need there is no need to reinvent the wheel :-D
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
add a comment |
If you wanna stick on sbt 1.2.6 you can just use the latest version hseeberger/scala-sbt
which is 11.0.1_2.12.7_1.2.6
.
docker pull hseeberger/scala-sbt:11.0.1_2.12.7_1.2.6
The version number contains of the openjdk version (11.0.1), the scala version (2.12.7) and the sbt version (1.2.6). If that's all you need there is no need to reinvent the wheel :-D
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
add a comment |
If you wanna stick on sbt 1.2.6 you can just use the latest version hseeberger/scala-sbt
which is 11.0.1_2.12.7_1.2.6
.
docker pull hseeberger/scala-sbt:11.0.1_2.12.7_1.2.6
The version number contains of the openjdk version (11.0.1), the scala version (2.12.7) and the sbt version (1.2.6). If that's all you need there is no need to reinvent the wheel :-D
If you wanna stick on sbt 1.2.6 you can just use the latest version hseeberger/scala-sbt
which is 11.0.1_2.12.7_1.2.6
.
docker pull hseeberger/scala-sbt:11.0.1_2.12.7_1.2.6
The version number contains of the openjdk version (11.0.1), the scala version (2.12.7) and the sbt version (1.2.6). If that's all you need there is no need to reinvent the wheel :-D
answered Nov 15 '18 at 15:20
TobiSHTobiSH
1,5971226
1,5971226
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
add a comment |
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
thanks - now I have 2 solutions for my problem;)
– pme
Nov 15 '18 at 15:43
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%2f53318465%2fdocker-speed-up-sbt-image-getting-org-scala-sbt-sbt-1-2-6-this-may-take-some%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
Without having a closer look.
docker diff
might give you a hint what is going on.– TobiSH
Nov 15 '18 at 13:24