Skip to content

fix: remove yugabyte --advertise_address=0.0.0.0 for DDL issues #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
redpanda-f merged 1 commit into from
Mar 10, 2026
Merged

fix: remove yugabyte --advertise_address=0.0.0.0 for DDL issues #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/commands/start/yugabyte/mod.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,13 +96,16 @@ fn spawn_yugabyte_instance(

// Add YugabyteDB startup command with full configuration
// CRITICAL: --base_dir must match the volume mount location
// NOTE: --advertise_address is intentionally omitted. Setting it to 0.0.0.0 caused
// seed DDL via yugabyted to succeed but left the YCQL/YSQL proxies unreachable from
// other containers. Without --advertise_address, yugabyted auto-detects the container's
// IP on the Docker bridge network, which is reachable by other containers on the same network.
docker_args.extend_from_slice(&[
"/yugabyte/bin/yugabyted",
"start",
"--base_dir=/home/foc-user/yb_base",
"--ui=true",
"--callhome=false",
"--advertise_address=0.0.0.0",
"--master_flags=rpc_bind_addresses=0.0.0.0",
"--tserver_flags=rpc_bind_addresses=0.0.0.0,pgsql_proxy_bind_address=0.0.0.0:5433,cql_proxy_bind_address=0.0.0.0:9042",
"--daemon=false",
Expand Down