build marked as error when it's actually successful
See original GitHub issueI’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:
- Created 9 years ago
- Comments:5 (2 by maintainers)
Top 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 >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @marcuslonnberg, I’m experiencing this issue as well, on version 1.3.8. Do you know of a fix?
Which version of sbt-docker plugin you are using? I was running into same issue with version
1.5.0
. It seem to work with1.8.0
though.addSbtPlugin("se.marcuslonnberg" % "sbt-docker" % "1.8.0")