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.

Dependency resolution fails in Docker

See original GitHub issue

I have a few dependencies that are hosted on an on-premise Nexus server, a resolver for these dependencies has been added and there is no issue building the project. However when trying to build the project using the openjdk:8-jre image module resolution is failing for those dependencies.

Furthermore all dependency resolution is incredibly slow, taking easily 5-6x the normal time of resolution.

sbt version: 0.13.15

Issue Analytics

State:
Created 6 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

4reactions

themeriuscommented, Dec 3, 2017

I have the same problem: sbt is very slow in dependency resolution when executed within a docker container. Any ideas?

0reactions

eed3si9ncommented, Aug 6, 2018

Thanks everyone for sharing the experience on Docker. It seems like there aren’t much sbt can do, I am going to close this issue.

Top Results From Across the Web

Unable to resolve dependency when docker-compose build

From the dependency error section below, think the issue is due to not being able to resolve a dependency tree and resolving a...

[4.6.2] Docker build failed - Could not resolve dependencies

* major release, but I can't build docker image for 4.6.0 and upper. build 19-Feb-2021 21:53:46 [ERROR] Failed to execute goal on project ......

SOLVED: Docker build “Could not resolve 'archive.ubuntu ...

I get the error as seen in the screen shot below. Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'archive.

Dependency Scanning - GitLab Docs

This error occurs when the Docker version that runs the dependency scanning job is 19.03.0 . Consider updating to Docker 19.03.1 or greater....

Control startup and shutdown order in Compose

Compose always starts and stops containers in dependency order, where dependencies are determined by depends_on , links , volumes_from , and network_mode: ...