failed to solve: archive/tar: unknown file mode ?rwxr-xr-x while following official tutorial

[ra2dd]

Description

I get this console output while trying to create image using docker following official documentation:

[+] Building 16.4s (8/11)                                                              docker:default
 => [internal] load build definition from Dockerfile                                             0.0s
 => => transferring dockerfile: 188B                                                             0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1                        2.1s
 => [auth] docker/dockerfile:pull token for registry-1.docker.io                                 0.0s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:a57df69d0ea827fb7266491f2813635d  0.0s
 => [internal] load metadata for docker.io/library/node:18-alpine                                0.0s
 => [internal] load .dockerignore                                                                0.0s
 => => transferring context: 2B                                                                  0.0s
 => [1/4] FROM docker.io/library/node:18-alpine                                                  0.0s
 => ERROR [internal] load build context                                                         14.0s
 => => transferring context: 52.90MB                                                            14.0s
------
 > [internal] load build context:
------
ERROR: failed to solve: archive/tar: unknown file mode ?rwxr-xr-x

Dockerfile:

# syntax=docker/dockerfile:1

FROM node:18-alpine
WORKDIR /app
COPY . .
RUN yarn install --production
CMD ["node", "src/index.js"]
EXPOSE 3000

Reproduce

1. git clone https://github.com/docker/getting-started-app.git
2. docker build -t getting-started .
3. docker run -dp 127.0.0.1:3000:3000 -w /app --mount "type=bind,src=$pwd,target=/app" node:18-alpine sh -c "yarn install && yarn run dev"
4. Stop the container
5. docker build -t getting-started .

Expected behavior

Should build an image.

docker version

Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:48:43 2024
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.30.0 (149282)
 Engine:
  Version:          26.1.1
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       ac2de55
  Built:            Tue Apr 30 11:48:28 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.29
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.8.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 2
 Server Version: 26.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.146.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 7.444GiB
 Name: docker-desktop
 ID: 2fd69fc4-4772-448e-afdb-2e608219d290
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

B4CDA7F3-D311-4B04-9568-259F15E34172/20240521101959

Additional Info

After deleting all containers and images associated with folder the error persist.

Link to the tutorial that I'm running commands from

[LucianCheve]

I also get the same error. I'm doing the same tutorial

[wangchunpeng]

=> CACHED [ 1/10] FROM docker.io/library/ubuntu:jammy 0.0s
=> ERROR [internal] load build context 6.0s
=> => transferring context: 288.17MB 6.0s
=> CANCELED [ 2/10] RUN apt-get update -y 6.3s

[internal] load build context:

---

ERROR: failed to solve: archive/tar: unknown file mode ?rwxr-xr-x

[wangchunpeng]

got the same problem， Docker Desktop 4.30.0 (149282) is currently the newest version available.

[david-engelmann]

is there a workaround yet?

[paprika-wasabi]

I also got the same problem with Window Local machine.
I tried with Powershell and git bash got the same error
#6 ERROR: archive/tar: unknown file mode ?rwxr-xr-x
then I tried with WSL (Window subsystem linux) so now it is working.

[SuS-PascalR]

Same error here.

[david-engelmann]

was able to build with docker compose -f .devcontainer/docker-compose.yml up -d --build but still busted from a devcontainer perspective

[giodestone]

Having same issue.

I was trying to fix another issue from Node about missing a missing dependency (rollup/rollup-linux-x64-gnu), thought it may have been something to do with creating the project on a Windows host and trying to run it in a Linux container, so I tried recreating the vite project in a node container - and then ran into this instead!

I tried to clear my docker cache (docker system prune -a) and restart the Docker Engine via desktop but it didn't work.

I'm running Windows 10 22H2 and latest Docker 4.30.0.

What I did was:

1. Created a dev container from a folder using VS Code's Dev Environments. The container was node:18 with no additions offered by VS Code.
2. Installed vite using npm
3. Created a vite project for React and Typescript
4. Ran advised commands after creating a vite project.
5. Stopped the container.
6. Cleared the contents of the original folder.
7. Copied the contents of the directory created by vite.
8. Ran docker compose up.

Result:

...
=> CACHED [app-frontend 2/6] WORKDIR /notes-app-frontend                                                                                                                                                                   
------
 > [app-frontend internal] load build context:
------
failed to solve: archive/tar: unknown file mode ?rwxr-xr-x

Dockerfile:

FROM node:20-alpine
WORKDIR /notes-app-frontend
COPY package.json .
COPY package-lock.json .
RUN npm install
COPY . .
CMD ["npm", "run", "dev"]

Section of docker-compose.yml (note: I am not using watch):

...
app-frontend:
    depends_on:
      - app-backend
    container_name: notes-app-frontend
    build: ./notes-app-frontend
    restart: on-failure
    env_file: ./.env
    environment:
      - APP_FRONT_DOCKER_PORT=$APP_FRONT_DOCKER_PORT
    ports:
    - $APP_FRONT_LOCAL_PORT:$APP_FRONT_DOCKER_PORT
    volumes:
      - ./notes-app-frontend:/notes-app-frontend
    develop:
      watch:
        - action: sync
          path: ./notes-app-frontend
          target: /src/
        - action: rebuild
          path: ./notes-app-frontend/package.json
        - action: rebuild
          path: .env
..

The front end folder structure:

full-stack-notes-docker
- docker-compose.yml
- ...
- - notes-app-frontend
- - - node_modules
- - - - ...
- - - public
- - - - ...
- - - src
- - - - ...
- - .env.sample
- - eslintrct.cjs
- - .gitignore
- - Dockerfile
- - index.html
- - package-lock.json
- - package.json
- - README.md
- - tsconfig.json
- - tsconfig.node.json
- - vite.config.ts

[cottley]

From what I can tell, it looks like something is corrupting the attributes of files accessed via bind mounts when the node_modules is being generated inside a Linux image but being built on Windows. If you recreate the node_modules folder outside of docker, in Windows directly, using npm install, you should be able to build the image.

Alternately, if you copy the code without the node_modules folder into your image from your Dockerfile and run an npm install as a step in the build from the code directory, that should work.