You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: combine Docker compatibility sections in deployment guide (#784)
Merged "Manifest Not Found" and "Docker Version Requirements" sections
into a single "Docker Compatibility" section for better organization
and reduced nesting levels.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <[email protected]>
Copy file name to clipboardExpand all lines: mintlify/get-started/install/deploy-with-docker.mdx
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,10 +21,13 @@ For production deployments:
21
21
22
22
## Troubleshooting
23
23
24
-
### Docker Version Requirements
24
+
### Docker Compatibility
25
25
26
-
Docker version must be at least [20.10.24](https://docs.docker.com/engine/release-notes/20.10/#201024).
27
-
For older versions, pass `--security-opt seccomp=unconfined` to `docker run` to avoid the `pthread_create failed` error.
26
+
Docker version must be at least 20.10.24. We recommend using the [latest Docker version](https://docs.docker.com/engine/install/). If you cannot upgrade Docker, pass `--security-opt seccomp=unconfined` to `docker run` as a best effort to avoid the `pthread_create failed` error.
27
+
28
+
If you encounter a "manifest not found" error, this may be due to:
29
+
-**Architecture mismatch**: The docker image only supports `linux/amd64` and `linux/arm64` architectures. If it doesn't match your OS architecture, you may supply `--platform linux/amd64` as a best effort.
30
+
-**Outdated Docker version**: Your Docker version is too old and doesn't support manifest lists.
28
31
29
32
### Air-gapped Environment
30
33
@@ -52,14 +55,6 @@ If you see `bind: address already in use` error, it means the port 8080 is alrea
52
55
- If you **run Bytebase inside Docker on Linux**, then you need to supply the additional `--network host` flags in `docker run` command. This allows Bytebase to connect to database instance running on the same host with `localhost`.
53
56
- If you **run Bytebase inside Docker Desktop on Mac** , then you need to use `host.docker.internal` to connect to database instance running on the same host.
54
57
55
-
### Manifest Not Found
56
-
57
-
There may be a few reasons the manifest file is not found:
58
-
59
-
- The docker image only supports `linux/amd64` and `linux/arm64` arch. If it doesn't match your OS arch, you may supply
60
-
`--platform linux/amd64` as a best effort.
61
-
- Your Docker version is too old and doesn't support manifest list. Please [install the latest Docker version](https://docs.docker.com/engine/install/).
62
-
63
58
### Colima Support
64
59
65
60
Due to the vm mechanism of [Colima](https://github.com/abiosoft/colima), try to use the `--mount` option when starting colima as shown below:
0 commit comments