--security-opt seccomp=unconfined
to docker run
, otherwise, you will get pthread_create failed
error.
registry.cn-shanghai.aliyuncs.com/bytebase/bytebase:3.8.1
.
bind: address already in use
error, it means the port 8080 is already in use on your host. You need to either stop the existing process using the port or configure Bytebase to use a different port via --publish <<YOUR_PORT>>:8080
.
--network host
flags in docker run
command. This allows Bytebase to connect to database instance running on the same host with localhost
.host.docker.internal
to connect to database instance running on the same host.linux/amd64
and linux/arm64
arch. If it doesn’t match your OS arch, you may supply
--platform linux/amd64
as a best effort.--mount
option when starting colima as shown below:
bb.yaml
describing the minimal components and configuration required to run Bytebase in Kubernetes.
helm upgrade
command to upgrade the bytebase version or configuration.
Ingress-Nginx Controller
according to your environment.
spec.templates.spec.containers.env
section:
--set bytebase.option.existingPgURLSecret
and --set bytebase.option.existingPgURLSecretKey
to specify the secret key and secret name instead of --set "bytebase.option.external-url"={NEW_EXTERNAL_URL}
. See more details in Bytebase - Artifact Hub.
AWS Fargate (serverless)
under Infrastructure.bytebase/bytebase:latest
and Container port 8080
.Service
as the Application type, choose the task definition you created in the previous step, give it a name such as bytebase-service
.Version 3.8.1 has started on port 8080 🚀
, it means Bytebase is running.