【发布时间】:2022-02-26 10:18:12
【问题描述】:
我正在尝试在 Github Actions 运行器中构建和标记 docker 映像,并从运行器中收到此错误
unable to prepare context: path " " not found
Error: Process completed with exit code 1.
我已经解决了 StackOverflow 上的所有其他类似问题并实施了它们,但仍然没有前进的道路。
有趣的是,我有其他微服务使用类似的工作流程,并且 Dockerfile 工作得非常好。
我的工作流程
name: some-tests
on:
pull_request:
branches: [ main ]
jobs:
tests:
runs-on: ubuntu-latest
env:
AWS_REGION: us-east-1
IMAGE_NAME: service
IMAGE_TAG: 1.1.0
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Create cluster
uses: helm/kind-action@v1.2.0
- name: Read secrets from AWS Secrets Manager into environment variables
uses: abhilash1in/aws-secrets-manager-action@v1.1.0
id: read-secrets
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: ${{ env.AWS_REGION }}
secrets: |
users-service/secrets
parse-json: true
- name: Build and Tag Image
id: build-image
run: |
# Build a docker container and Tag
docker build --file Dockerfile \
--build-arg APP_API=$USERS_SERVICE_SECRETS_APP_API \
-t $IMAGE_NAME:$IMAGE_TAG .
echo "::set-output name=image::$IMAGE_NAME:$IMAGE_TAG"
- name: Push Image to Kind cluster
id: kind-cluster-image-push
env:
KIND_IMAGE: ${{ steps.build-image.outputs.image }}
CLUSTER_NAME: chart-testing
CLUSTER_CONTROLLER: chart-testing-control-plane
run: |
kind load docker-image $KIND_IMAGE --name $CLUSTER_NAME
docker exec $CLUSTER_CONTROLLER crictl images
Dockerfile*
FROM node:14 AS base
WORKDIR /app
FROM base AS development
COPY .npmrc .npmrc
COPY package.json ./
RUN npm install --production
RUN cp -R node_modules /tmp/node_modules
RUN npm install
RUN rm -f .npmrc
COPY . .
FROM development AS builder
COPY .npmrc .npmrc
RUN yarn run build
RUN rm -f .npmrc
RUN ls -la
FROM node:14-alpine AS production
# Install curl
RUN apk update && apk add curl
COPY --from=builder /tmp/node_modules ./node_modules
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/package.json ./
ARG APP_API
# set environmental variables
ENV APP_API=$APP_API
EXPOSE ${PORT}
CMD [ "yarn", "start" ]
我猜问题出在构建命令之类的东西上,这些是我尝试过的不同的东西
我将 --file 明确地与句点(.)一起使用*
docker build --file Dockerfile \
--build-arg APP_API=$USERS_SERVICE_SECRETS_APP_API \
-t $IMAGE_NAME:$IMAGE_TAG .
echo "::set-output name=image::$IMAGE_NAME:$IMAGE_TAG"
我只用了句号 (.)
docker build \
--build-arg APP_API=$USERS_SERVICE_SECRETS_APP_API \
-t $IMAGE_NAME:$IMAGE_TAG .
echo "::set-output name=image::$IMAGE_NAME:$IMAGE_TAG"
我使用了 Dockerfile 的相对路径(./Dockerfile)
docker build --file ./Dockerfile \
--build-arg APP_API=$USERS_SERVICE_SECRETS_APP_API \
-t $IMAGE_NAME:$IMAGE_TAG .
echo "::set-output name=image::$IMAGE_NAME:$IMAGE_TAG"
我在句点 (./) 中使用了相对路径
docker build \
--build-arg APP_API=$USERS_SERVICE_SECRETS_APP_API \
-t $IMAGE_NAME:$IMAGE_TAG ./
echo "::set-output name=image::$IMAGE_NAME:$IMAGE_TAG"
我已经用尽了我从 SO 中读到的所有内容
【问题讨论】:
-
您未能包括您提供的众多步骤中的哪一个产生了该消息,但我怀疑
$USERS_SERVICE_SECRETS_APP_API正在扩展并引入您不想要的东西。有两种方法可以解决这个问题:(a)引用 arg 并查看它是否在您的步骤中修复它--build-arg "APP_API=$USERS_SERVICE_SECRETS_APP_API"(b)set -x并查看 shell 看到了什么;我强烈建议您也引用"$IMAGE_NAME:$IMAGE_TAG",因为这样让他们光秃秃的只有风险,没有回报 -
@mdaniel 我已经尝试在 --build-arg 值周围加上引号,但仍然无济于事
标签: node.js docker kubernetes dockerfile github-actions