question-mark
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.

build marked as error when it's actually successful

See original GitHub issue

I’m seeing the following:

[info] Successfully built :hash1
[info] Removing intermediate container :hash2
java.lang.RuntimeException: Could not parse image id
    at scala.sys.package$.error(package.scala:27)
    at sbtdocker.DockerBuilder$.buildImage(DockerBuilder.scala:87)
    at sbtdocker.DockerBuilder$.apply(DockerBuilder.scala:23)
    at sbtdocker.Plugin$$anonfun$baseDockerSettings$1.apply(Plugin.scala:27)
    at sbtdocker.Plugin$$anonfun$baseDockerSettings$1.apply(Plugin.scala:22)
    at scala.Function6$$anonfun$tupled$1.apply(Function6.scala:35)
    at scala.Function6$$anonfun$tupled$1.apply(Function6.scala:34)
    at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
    at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:42)
    at sbt.std.Transform$$anon$4.work(System.scala:64)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237)
    at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18)
    at sbt.Execute.work(Execute.scala:244)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237)
    at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160)
    at sbt.CompletionService$$anon$2.call(CompletionService.scala:30)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
[error] (*:docker) Could not parse image id

Looks like the code to parse the image id fails if there’s a “removing intermediate container” line after “successfully built” since it only looks at the very last line of output: https://github.com/marcuslonnberg/sbt-docker/blob/master/src/main/scala/sbtdocker/DockerBuilder.scala#L82

I’m only seeing this transiently.

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

8reactions
elonybearcommented, Oct 26, 2020

Hi @marcuslonnberg, I’m experiencing this issue as well, on version 1.3.8. Do you know of a fix?

[info] #13 writing image sha256:ea4317746ead7d49f458df4f58a6d94625d99a8c60716ecaa2581a3ecc7121c6 done
[info] #13 DONE 1.8s
[error] java.lang.RuntimeException: Could not parse image id
[error] 	at scala.sys.package$.error(package.scala:30)
[error] 	at sbtdocker.DockerBuild$.build(DockerBuild.scala:99)
[error] 	at sbtdocker.DockerBuild$.buildAndTag(DockerBuild.scala:72)
[error] 	at sbtdocker.DockerBuild$.apply(DockerBuild.scala:45)
[error] 	at sbtdocker.DockerBuild$.apply(DockerBuild.scala:24)
[error] 	at sbtdocker.DockerSettings$.$anonfun$baseDockerSettings$1(DockerSettings.scala:17)
[error] 	at scala.Function1.$anonfun$compose$1(Function1.scala:49)
[error] 	at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:62)
[error] 	at sbt.std.Transform$$anon$4.work(Transform.scala:67)
[error] 	at sbt.Execute.$anonfun$submit$2(Execute.scala:281)
[error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:19)
[error] 	at sbt.Execute.work(Execute.scala:290)
[error] 	at sbt.Execute.$anonfun$submit$1(Execute.scala:281)
[error] 	at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:178)
[error] 	at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error] 	at java.lang.Thread.run(Thread.java:748)
[error] (orion-feature-pipeline / docker) Could not parse image id
[error] Total time: 14 s, completed Oct 26, 2020 8:09:59 AM
4reactions
ukudtarkarcommented, Nov 25, 2020

Which version of sbt-docker plugin you are using? I was running into same issue with version 1.5.0. It seem to work with 1.8.0 though. addSbtPlugin("se.marcuslonnberg" % "sbt-docker" % "1.8.0")

Read more comments on GitHub >

github_iconTop Results From Across the Web

Successful Jenkins Build marked as failed - Stack Overflow
One particularly annoying issue is the build server marking builds as "failed" (e-mail notification and everything) even though no failure reason at all...
Read more >
Pipeline activities being marked as failed even though build is ...
Summary Builds are being marked as Failed (as shown in the pipelineactivity) even though the build logs all show SUCCESS.
Read more >
Build succeeded, but 7 Errors - MSDN
This will show you the success or failure of each project in the solution (or whatever you last built). For example the last...
Read more >
Understanding Success Criterion 1.3.1 - W3C
The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved...
Read more >
Build Succeeded but Error List Has Errors
Hi Mark, what sort of project do you have? Is it a traditional csproj with a "References" node, or an SDK-Style project with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found