Docker容器中Maven构建失败排查及AWS EC2部署问题解决
Maven构建报错"No goals have been specified for this build"及Docker-compose构建优化解决过程
在AWS EC2实例上通过docker-compose搭建应用上线流水线时,执行docker-compose -f docker-compose-java.yml up出现Maven构建失败,错误提示:No goals have been specified for this build。
错误日志
Starting bookinghub ... done Attaching to bookinghub bookinghub | [INFO] Scanning for projects... bookinghub | [INFO] ------------------------------------------------------------------------ bookinghub | [INFO] BUILD FAILURE bookinghub | [INFO] ------------------------------------------------------------------------ bookinghub | [INFO] Total time: 0.141 s bookinghub | [INFO] Finished at: 2022-11-23T22:22:23Z bookinghub | [INFO] ------------------------------------------------------------------------ bookinghub | [ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] bookinghub | [ERROR] bookinghub | [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. bookinghub | [ERROR] Re-run Maven using the -X switch to enable full debug logging. bookinghub | [ERROR] bookinghub | [ERROR] For more information about the errors and possible solutions, please read the following articles: bookinghub | [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException bookinghub exited with code 1
初始配置文件
Dockerfile
FROM maven:3.8.6-openjdk-18 AS MAVEN_BUILD RUN microdnf install git -y RUN mkdir ~/.ssh COPY id_rsa /root/.ssh/id_rsa COPY known_hosts /etc/ssh/known_hosts WORKDIR /root/.ssh/ RUN chmod 400 id_rsa RUN ssh-keyscan gitlab.com >> ~/.ssh/known_hosts RUN mkdir ~/repositorio WORKDIR /repositorio/ RUN git clone git@gitlab.com:booking_hub/grupo_04_bookinghub.git RUN cd grupo_04_bookinghub/backend/APIrest/APIrest RUN mvn clean install "-Dmaven.test.skip=true" && mvn package FROM openjdk:17-slim WORKDIR /app COPY --from=MAVEN_BUILD /repositorio/target/APIrest-*.jar /app/APIrest.jar ENTRYPOINT ["java","-Dspring.profiles.active=dev", "-jar", "APIrest.jar"]
docker-compose-java.yml
version: "3.7" services: #outro container --- backend springweb: container_name: bookinghub build: . #preciso do Dockerfile para gerar a imagem ports: - "8080:8080" networks: - servers environment: SPRING_PROFILES_ACTIVE: dev networks: servers: driver: bridge
pom.xml
<?xml version="1.0" encoding="UTF-8"?> <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 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.7.5</version> <relativePath/> <!-- lookup parent from repository --> </parent> <groupId>br.com.APIrest</groupId> <artifactId>APIrest</artifactId> <version>0.0.1-SNAPSHOT</version> <name>APIrest</name> <description>project for Spring Boot APIrest</description> <properties> <java.version>17</java.version> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-jpa</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-security</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <dependency> <groupId>com.h2database</groupId> <artifactId>h2</artifactId> <scope>runtime</scope> </dependency> <dependency> <groupId>com.mysql</groupId> <artifactId>mysql-connector-j</artifactId> <scope>runtime</scope> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-test</artifactId> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>
预期目标:每次执行docker-compose时,容器自动完成git克隆、项目构建并运行jar包。
问题排查与解决
@EDIT1:Docker-compose镜像重建问题
发现docker-compose默认不会每次运行都重新构建镜像,执行sudo docker system prune -a --volumes清理所有镜像和卷后重新运行,此时错误变为数据库连接失败(符合预期,因EC2未连接MySQL RDS或容器)。
强制docker-compose重新构建镜像的方法:
- 启动时强制构建:
docker-compose -f docker-compose-java.yml up --build - 单独构建镜像(不启动容器):
docker-compose -f docker-compose-java.yml build --no-cache springweb(--no-cache确保完全重新构建,不使用缓存层)
@EDIT2:Dockerfile修正解决Maven构建错误
修改后的Dockerfile:
FROM maven:3.8.6-openjdk-18 AS MAVENBUILD RUN microdnf install git -y RUN mkdir ~/.ssh COPY id_rsa /root/.ssh/id_rsa COPY known_hosts /etc/ssh/known_hosts WORKDIR /root/.ssh/ RUN chmod 400 id_rsa RUN ssh-keyscan gitlab.com >> ~/.ssh/known_hosts RUN mkdir ~/repositorio WORKDIR /repositorio/ RUN git clone git@gitlab.com:booking_hub/grupo_04_bookinghub.git WORKDIR /repositorio/grupo_04_bookinghub/backend/APIrest/APIrest RUN mvn clean install -Dmaven.test.skip=true && mvn package FROM openjdk:17 WORKDIR /app COPY --from=MAVENBUILD /repositorio/grupo_04_bookinghub/backend/APIrest/APIrest/target/APIrest-0.0.1-SNAPSHOT.jar /app/APIrest.jar ENTRYPOINT ["java","-Dspring.profiles.active=dev", "-jar", "APIrest.jar"]
修正点说明:
- 原Dockerfile中
RUN cd grupo_04_bookinghub/backend/APIrest/APIrest是单独的RUN指令,Docker的每个RUN指令都在独立的容器层执行,cd操作不会影响后续RUN的工作目录,导致Maven在/repositorio目录下执行(该目录无pom.xml),触发构建目标缺失错误。改用WORKDIR切换目录,确保后续Maven命令在正确的项目目录下执行。 - 修正了COPY jar包的路径,原路径
/repositorio/target/APIrest-*.jar错误,改为项目实际构建后的jar包路径/repositorio/grupo_04_bookinghub/backend/APIrest/APIrest/target/APIrest-0.0.1-SNAPSHOT.jar。
修改后应用可在Docker容器中正常运行,问题解决。
内容的提问来源于stack exchange,提问作者FelipeGodoy96
相关产品推荐
相关产品推荐

