简体   繁体   English

spotify docker / dockerfile maven插件[错误]复制失败

[英]spotify docker/dockerfile maven plugin [ERROR] Copy failed

I am trying to execute the mvn clean package docker:build on my project it fails with the following error 我试图在我的项目上执行mvn clean package docker:build它失败并出现以下错误

ERROR] Failed to execute goal com.spotify:docker-maven-plugin:1.1.0:build (default-cli) on project mma-access-management-auth-server: Exception caught: COPY failed: stat /var/lib/docker/tmp/docker-builder181535370/mma-access-management-app-1.0.0-SNAPSHOT.jar: no such file or directory -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.spotify:docker-maven-plugin:1.1.0:build (default-cli) on project mma-access-management-auth-server: Exception caught at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.int 错误]无法在项目mma-access-management-auth-server上执行目标com.spotify:docker-maven-plugin:1.1.0:build(default-cli):捕获的异常:COPY失败:stat / var / lib / docker / tmp / docker-builder181535370 / mma-access-management-app-1.0.0-SNAPSHOT.jar:无此类文件或目录-> [帮助1] org.apache.maven.lifecycle.LifecycleExecutionException:无法执行目标com .spotify:docker-maven-plugin:1.1.0:在项目mma-access-management-auth-server上构建(default-cli):org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor。 java:213)在org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)在org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)在org.apache org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)上的.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)在org.apache.maven.lifecycle.int ernal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Lau org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)处的ernal.builder.singleThreaded.SingleThreadedBuilder.java(SingleThreadedBuilder.java:51)(org.apache.maven.DefaultMaven.doExecute(DefaultMaven。 java:309)位于org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)位于org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)位于org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)在org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)在org.apache.maven.cli.MavenCli.main(MavenCli.java:194)在sun.reflect。位于sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)处的NativeMethodAccessorImpl.invoke0(本地方法),位于java.lang.reflect.Method.invoke(方法。 java:498)在org.codehaus.plexus.classworlds.launcher.Launcher.launch增强(Launcher.java:289)在org.codehaus.plexus.classworlds.launcher.Launcher.launch(Lau ncher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Exception caught at com.spotify.docker.AbstractDockerMojo.execute (AbstractDockerMojo.java:151) at com.spotify.docker.BuildMojo.execute (BuildMojo.java:324) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)处的org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)的ncher.java:229) :org.apache.maven.plugin.MojoExecutionException:在org.com.spotify.docker.BuildMojo.execute(BuildMojo.java:324)处com.spotify.docker.AbstractDockerMojo.execute(AbstractDockerMojo.java:151)处捕获到异常。 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)处org.apache.maven.lifecycle.internal.MojoExecutor处的apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)在org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)在org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)上执行(MojoExecutor.java:154)在org.apache.maven.lifecycle的org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)处 .internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)上的.internal.builder.singlethreaded.SingleThreadedBuilder.java(51)在org.apache.maven.DefaultMaven.doExecute(DefaultMaven) .java:309),位于org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194),位于org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107),位于org.apache.maven.cli.MavenCli。在org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)在org.apache.maven.cli.MavenCli.main(MavenCli.java:194)处执行(MavenCli.java:955)在sun.reflect .sun.reflect上的.NativeMethodAccessorImpl.invoke0(本机方法).java.lang.reflect.Method.invoke(方法上).NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)在sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) .java:498)(位于org.codehaus.plexus.classworlds.launcher.Launcher.launch上)(Launcher.java:289)位于org.codehaus.plexus.classworlds.launcher.Launcher.launch上 (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: com.spotify.docker.client.exceptions.DockerException: COPY failed: stat /var/lib/docker/tmp/docker-builder181535370/mma-access-management-app-1.0.0-SNAPSHOT.jar: no such file or directory (org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)处(Launcher.java:229)在org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)创建人:com.spotify.docker.client.exceptions.DockerException:复制失败:stat /var/lib/docker/tmp/docker-builder181535370/mma-access-management-app-1.0.0-SNAPSHOT.jar:没有这样的文件或目录

This is my pom.xml 这是我的pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
    <groupId>com.mma</groupId>
    <artifactId>mma-access-management-parent</artifactId>
    <version>1.0.0-SNAPSHOT</version>
</parent>
<artifactId>mma-access-management-auth-server</artifactId>
<packaging>jar</packaging>
<dependencies>
    <dependency>
        <groupId>${project.groupId}</groupId>
        <artifactId>mma-access-management-rest-api</artifactId>
        <version>${project.version}</version>
    </dependency>
</dependencies>
<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
</properties>
<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
            <version>1.5.8.RELEASE</version>
            <executions>
                <execution>
                    <goals>
                        <goal>repackage</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
        <plugin>
            <groupId>com.spotify</groupId>
            <artifactId>docker-maven-plugin</artifactId>
            <version>1.1.0</version>
            <configuration>
                <imageName>mma/${project.artifactId}</imageName>
                <imageTags>
                    <imageTag>${project.version}</imageTag>
                    <imageTag>latest</imageTag>
                </imageTags>
                <dockerDirectory>dockerfile</dockerDirectory>
                <resources>
                    <resource>
                        <targetPath>/</targetPath>
                        <directory>${project.build.directory}</directory>
                        <include>${project.build.finalName}.jar</include>
                    </resource>
                </resources>
            </configuration>
        </plugin>
    </plugins>
</build>

This is my Dockerfile 这是我的Dockerfile

FROM openjdk:8u131-jdk-alpine
ENV targetDir /usr/local/access-management-app-1.0.0-SNAPSHOT.jar
ENV srcDir .
ENV jarFile mma-access-management-app-1.0.0-SNAPSHOT.jar
RUN mkdir ${targetDir}
COPY ${srcDir}/${jarFile} ${targetDir}
WORKDIR ${targetDir}
CMD ["java", "-jar", "mma-access-management-app-1.0.0-SNAPSHOT.jar"]
EXPOSE 8080/tcp

I don't know that is going wrong. 我不知道那是错的。 I also tried to use the dockerfile plugin from spotify which also failed. 我还尝试使用Spotify的dockerfile插件,该插件也失败了。

The jar file of the maven build ${project.build.finalName}.jar differs from the one you have defined in the Dockerfile . Maven build ${project.build.finalName}.jar的jar文件不同于您在Dockerfile定义的jar文件。

Adjust the specified jar filename in the Dockerfile to match the jar of the maven build and it will work. 调整Dockerfile中指定的jar文件名,使其与Maven构建的jar文件匹配,即可使用。

FROM openjdk:8u131-jdk-alpine
ENV targetDir /usr/local/access-management-auth-server-1.0.0-SNAPSHOT.jar
ENV srcDir .
ENV jarFile mma-access-management-auth-server-1.0.0-SNAPSHOT.jar
RUN mkdir ${targetDir}
COPY ${srcDir}/${jarFile} ${targetDir}
WORKDIR ${targetDir}
CMD ["java", "-jar", "mma-access-management-auth-server-1.0.0-SNAPSHOT.jar"]
EXPOSE 8080/tcp

Does not look like a issue with the spotify plugin. 看起来不像Spotify插件有问题。 The docker build is failing at COPY ${srcDir}/${jarFile} ${targetDir} I guess the srcDir points to the src folder whereas the jar will be present in the target folder. COPY ${srcDir}/${jarFile} ${targetDir} build在COPY ${srcDir}/${jarFile} ${targetDir}我猜srcDir指向src文件夹,而jar会出现在target文件夹中。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 使用 spotify/dockerfile-maven-plugin 推送 docker hub 时出错 - Error pushing docker hub using spotify/dockerfile-maven-plugin 如何配置com.spotify.dockerfile-maven-plugin在Docker Toolbox上运行? - How can I configure com.spotify.dockerfile-maven-plugin to run on Docker Toolbox? 与Spotify Maven插件和Docker一起使用时Fitnesse错误 - Fitnesse error when used with spotify maven plugin and docker spotify dockerfile-maven Dockerfile - spotify dockerfile-maven Dockerfile 未能执行目标 com.spotify:dockerfile-maven-plugin:1.3.6:build on project 'foo':无法构建映像: - Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.6:build on project 'foo': Could not build image: 未能执行目标 com.spotify:docker-maven-plugin:1.2.1:build (build-image) - Failed to execute goal com.spotify:docker-maven-plugin:1.2.1:build (build-image) docker-maven-plugin 没有创建 dockerfile - docker-maven-plugin not creating dockerfile 无法执行目标com.spotify:docker-maven-plugin:1.0.0:build捕获的异常:basedir src / main / docker不存在 - Failed to execute goal com.spotify:docker-maven-plugin:1.0.0:build Exception caught: basedir src/main/docker does not exist Spotify Dockerfile Maven AWS ECR - Spotify Dockerfile Maven AWS ECR docker maven插件错误 - docker maven plugin error
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM