| I am getting this same error in the following Jenkins version.
| org.jenkins-ci.main:jenkins-war:2.176.1 |
My command is as follows and the Dockerfile is actually named "dockerfile" (lower case 'd')
app = docker.build('newimage_190715');
The docker.build() call is actually building the docker image, but at the end, it gives an error,
Successfully built a1b2c3d4e5
Successfully tagged newimage_190715:latest
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.nio.file.NoSuchFileException: <path>/Dockerfile
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
To workaround the build failure, I created a symlink and the error disappeared.
$ ls -ltr
lrwxrwxrwx 1 xxxxxxxx 1234 10 Jul 15 22:00 Dockerfile -> dockerfile
Is there a dependency on the exact filename that Jenkins expects at some point in the build steps ? |