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

[Yu-SKun]

📦 Platform

Other

📦 Deploymenet mode

server db(lobe-chat-database image)

📌 Version

1.68.5

💻 Operating System

Windows

🌐 Browser

Chrome

🐛 Bug Description

I am pulling the source code from a GitHub repository locally on Windows 10, and then building a local Docker image using the WSL2 and Docker for Desktop environment with the following command: docker build -t lobe-chat-database-local -f Dockerfile.database --build-arg USE_CN_MIRROR=true .

[+] Building 24.3s (7/26) docker:desktop-linux
=> [internal] load build definition from Dockerfile.database 1.0s
=> => transferring dockerfile: 9.70kB 0.0s
=> [internal] load metadata for docker.io/library/busybox:latest 6.5s
=> [internal] load metadata for docker.io/library/node:22-slim 6.8s
=> [internal] load .dockerignore 0.8s
=> => transferring context: 138B 0.0s
=> CANCELED [base 1/2] FROM docker.io/library/node:22-slim@sha256:6bba748696297138f802735367bc78fea5cfe3b85019c74d2a930bc6c6b2fac4 14.0s
=> => resolve docker.io/library/node:22-slim@sha256:6bba748696297138f802735367bc78fea5cfe3b85019c74d2a930bc6c6b2fac4 0.7s
=> => sha256:6bba748696297138f802735367bc78fea5cfe3b85019c74d2a930bc6c6b2fac4 6.49kB / 6.49kB 0.0s
=> => sha256:7a6cc2b36be75212b8eccfe3291f61339dc5ef864699c303b2482f7d7b94a0ff 1.93kB / 1.93kB 0.0s
=> => sha256:7b74885e8fc3a1cebe89af170566e3d4e0fbcf58c80e4647c8a4b21e7b1a94a8 6.54kB / 6.54kB 0.0s
=> => sha256:7cf63256a31a4cc44f6defe8e1af95363aee5fa75f30a248d95cae684f87c53c 28.22MB / 28.22MB 4.6s
=> => sha256:afa0b3a9c7a1ca6822c527d1e1e5ebb2dde38e335e2d6075ca29d713a896e40e 3.31kB / 3.31kB 3.0s
=> => sha256:279386e9a5ff073669096edbdabda9187c3e63a429648e522e68ea9d11280900 48.31MB / 48.31MB 8.0s
=> => sha256:965993a606e35c8dfa13bc77c06b0081fce3f6be08ad8ee1ca3131e4dc06381c 1.71MB / 1.71MB 5.6s
=> => extracting sha256:7cf63256a31a4cc44f6defe8e1af95363aee5fa75f30a248d95cae684f87c53c 4.7s
=> => sha256:ffc500ec0db9c1ee11489eb0edafc701c4b77724fe00abee6c58cd3984564e09 448B / 448B 8.5s
=> => extracting sha256:afa0b3a9c7a1ca6822c527d1e1e5ebb2dde38e335e2d6075ca29d713a896e40e 0.0s
=> ERROR [internal] load build context 13.0s
=> => transferring context: 22.77MB 11.8s
=> [app 1/11] FROM docker.io/library/busybox:latest@sha256:498a000f370d8c37927118ed80afe8adc38d1edcbfc071627d17b25c88efcab0 10.5s
=> => resolve docker.io/library/busybox:latest@sha256:498a000f370d8c37927118ed80afe8adc38d1edcbfc071627d17b25c88efcab0 0.6s
=> => sha256:498a000f370d8c37927118ed80afe8adc38d1edcbfc071627d17b25c88efcab0 10.20kB / 10.20kB 0.0s
=> => sha256:42279ede3600b4e63af075a5e27d68232ff837d9cdcaba74feffc7ab0dfec0dc 610B / 610B 0.0s
=> => sha256:31311c5853a22c04d692f6581b4faa25771d915c1ba056c74e5ec82606eefdfa 459B / 459B 0.0s
=> => sha256:9c0abc9c5bd3a7854141800ba1f4a227baa88b11b49d8207eadc483c3f2496de 2.16MB / 2.16MB 2.1s
=> => extracting sha256:9c0abc9c5bd3a7854141800ba1f4a227baa88b11b49d8207eadc483c3f2496de 0.8s
[internal] load build context:

50 warnings found (use docker --debug to expand):

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "QWEN_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TAICHU_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NEXT_AUTH_SSO_PROVIDERS") (line 175)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_ACCESS_KEY_ID") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "HUNYUAN_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "INTERNLM_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "OPENROUTER_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PERPLEXITY_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SENSENOVA_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STEPFUN_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ANTHROPIC_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "GROQ_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NVIDIA_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ZEROONE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ZHIPU_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JINA_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "MISTRAL_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "MOONSHOT_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UPSTAGE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AI21_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AZURE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DEEPSEEK_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "GOOGLE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NOVITA_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "WENXIN_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3_ACCESS_KEY_ID") (line 180)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "GITEE_AI_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "GITHUB_TOKEN") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "HUGGINGFACE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "HIGRESS_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "OPENAI_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SPARK_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "VLLM_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "XAI_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "KEY_VAULTS_SECRET") (line 52)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NEXT_AUTH_SECRET") (line 175)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AI360_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "FIREWORKSAI_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TOGETHERAI_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "API_KEY_SELECT_MODE") (line 161)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "BAICHUAN_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "MINIMAX_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SILICONCLOUD_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SAMBANOVA_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TENCENT_CLOUD_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "KEY_VAULTS_SECRET") (line 170)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "S3_SECRET_ACCESS_KEY") (line 180)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CLOUDFLARE_API_KEY") (line 188)
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PPIO_API_KEY") (line 188)
ERROR: failed to solve: archive/tar: unknown file mode ?rwxr-xr-x
View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/yevudlep4sj8kot5b94a4qj21
 ELIFECYCLE  Command failed with exit code 1.

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @Yu-SKun

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

The error "archive/tar: unknown file mode ?rwxr-xr-x" typically occurs due to file permission issues when building Docker images on Windows, especially when using WSL2. This can happen if the file permissions in the Dockerfile or the build context are not compatible with Windows file systems.

Here are a few steps you can take to resolve this issue:

1. Check File Permissions: Ensure that the files in your build context have permissions that are compatible with both Linux and Windows. You might need to adjust the permissions using a Linux shell in WSL2.

2. Use a Compatible Base Image: Make sure the base image you are using is compatible with your environment. Sometimes switching to a different version of the base image can help.

3. Update Docker and WSL2: Ensure that both Docker Desktop and WSL2 are up to date, as updates often include fixes for compatibility issues.

4. Modify Dockerfile: If specific file permissions are set in the Dockerfile, try modifying them to more standard permissions that are less likely to cause issues on Windows.

5. Build Context: Ensure that your build context does not include unnecessary files that might have incompatible permissions. You can use a .dockerignore file to exclude such files.

If these steps do not resolve the issue, you might need to look into the specific file permissions set in the Dockerfile.database or any scripts being copied into the image, as these could be causing the compatibility issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}