Closed jerbasco1 closed 4 years ago
This error most likely occurs if downloading of o-saft.tgz failed.
In the Dockerfile it is defined as environment variable, see OSAFT_VM_SRC_OSAFT
Please check if you can download this file using wget, see in Dockerfile:
wget --no-check-certificate $OSAFT_VM_SRC_OSAFT -O $OSAFT_VM_TAR_OSAFT
If the system running the Dockerfile has no internet access, you can provide the file by defining OSAFT_VM_SRC_OSAFT as environment variable and pass like
docker build --build-arg "OSAFT_VM_SRC_OSAFT=..." ...
the docker VM then must have access to this URL.
Hope this helps.
The docker build successfully apt updates and downloads many things prior to that point, so I don't think connection is the issue.
I guess it's related to the known docker/alpine issue, see https://forums.docker.com/t/resolved-service-name-resolution-broken-on-alpine-and-docker-1-11-1-cs1/19307/23
There is already a dirty hack to prevent such race conditions (see nslookup in Dockerfile). I'll try to find a better workaround ...
The problem is the above-mentioned docker/alpine issue. The workaround is to prefetch name resolving in the Dockerfile, what a pain :-( Workaround can be found in Dockerfile.
The workaround is not guaranteed to work, unfortunately, but mainly does. It seem to be a race condition within alpines name resolution. That's why some make test
may also fail; then make -i test
must be used (manual change in the Dockerfile, sorry, not my fault).
nice work, that fixed it for me.
Getting an error building the docker image from the latest 19.01.19 zip
docker build --force-rm --rm -f Dockerfile -t owasp/o-saft .
window 10 1903 docker desktop community 2.1.0.5 stable