Docker build broken in current master
See original GitHub issueRunning the Docker build is currently broken in master
and also in 0.6.1
(but not in 0.6.0
).
Command:
docker build .
Error:
Step 20/37 : COPY --from=builder /opt/grobid-source/grobid-core/build/libs/grobid-core-*-onejar.jar ./grobid/grobid-core-onejar.jar
---> f50b25031de8
Step 21/37 : COPY --from=builder /opt/grobid-source/grobid-service/build/distributions/grobid-service-*.zip ./grobid-service.zip
COPY failed: no source files were specified
This seems to be caused by https://github.com/kermitt2/grobid/commit/683804d31eb5635468c93195a0bf79d7f91db1ed which disabled the creation of the distribution zip.
Might be good to add the Docker build as part of the CI build.
/cc @lfoppiano
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (4 by maintainers)
Top Results From Across the Web
docker: "build" requires 1 argument. See 'docker build --help'
Trying to follow the instructions for building a docker image from the docker website. FROM ubuntu:14.04 RUN apt-get update && apt-get install -y...
Read more >Set up Automated Builds - Docker Documentation
This default set builds from the Branch in your source code repository called master , and creates a Docker image tagged with latest...
Read more >Bug #1412343 “Command `docker build` is broken”
Firstly, as the shell wrapper for docker currently does `cd /apps/docker/1.3.3.001`, it breaks commands that assume current directory of ...
Read more >T208681 "docker-compose build" fails in master at wdqs ...
Looks like it's another overly specific dependency pinning error; here's the relevant snippet from the build log for current master:.
Read more >Dockerfile Strategies for Git - Baeldung
Secondly, this step will be cached on later builds, even when our repository changes. That's because the line with a RUN command is...
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
Yes that was before we migrated to gradle 6, I think with the install it was creating the zip file if I’m not wrong. Anyway, it seem that this change would fix this two issues in one go. So 👍.
40 minutes seem to be a bit high, why do you think that? The build for #629 (https://travis-ci.org/github/kermitt2/grobid/builds/721804752) ran for for over 7 minutes without Docker and over 8 minutes with Docker (although no tests in that case). The main difference is that caching artefacts across builds would be more difficult. I believe one way of doing it if it seems worth it, is to push / pull layers of the image (as the cloud CI servers don’t usually cache layers out of the box). I get more information on that (a colleague of mine used it for some project I believe).