! crawl4ai The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested 0.0s

[QuangTQV]

I am experiencing an issue when trying to run the Crawl4AI Docker image. The error message indicates that the requested image's platform does not match the detected host platform. Here are the details:

Host Platform: linux/amd64 Requested Image Platform: linux/arm64/v8 Error Message: exec /usr/local/bin/uvicorn: exec format error

[unclecode]

@QuangTQV Thanks for reporting this. I'll check and update within a day or two.

[jefcolbi]

Hi. I encounter the same error

[sol5288]

I have the same issue. I'm waiting for an update. thank you unclecode

[unclecode]

I've nearly found the issue. I hope to update the Dockerfile this week to support the nuances between the three operating systems. @QuangTQV @jefcolbi @sol5288

[jefcolbi]

Thank you. I tried building the container with docker build its succeeded but upon start it gives me an error.

  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/app/main.py", line 324, in <module>
    app.mount("/mkdocs", StaticFiles(directory="site", html=True), name="mkdocs")
  File "/usr/local/lib/python3.10/site-packages/starlette/staticfiles.py", line 56, in __init__
    raise RuntimeError(f"Directory '{directory}' does not exist")
RuntimeError: Directory 'site' does not exist

[unclecode]

@jefcolbi I think I need to move documents to another branch. The documentation you see is because I mounted library documentations to /mkdocs. To fix this, first install the mkdocs command line and then build the documentation, which will regenerate the site folder for you. If you have mkdocs, just run 'mkdocs build' and it will handle it. Thanks for pointing this out, I'll separate this from Docker to avoid such issues.