<@U0A71G31CDV> Does the allin1 test container imag...
# questions-and-troubleshooting
s
@Rocky Does the allin1 test container image expose or can expose the FE Proxy port for testing stream load requests without handling network complexity around redirect and docker networking
r
The StarRocks
allin1
test container image (e.g.,
starrocks/allin1-ubuntu
) primarily exposes the standard ports: 9030 (MySQL), 8030 (FE HTTP), and 8040 (BE HTTP). Regarding the FE Proxy (a component that handles Stream Load redirects by proxying data instead of sending a 307 redirect), here is the status for the
allin1
image: 1. Does it expose an FE Proxy port? The standard
allin1
image does not typically include the standalone Nginx-based FE Proxy found in Kubernetes Helm deployments (which uses port 8080). However, some newer community versions or configurations of the
allin1
image may set the FE HTTP port to 8080 or include the proxy process via
supervisord
. 2. Built-in FE Proxying (Recommended for Testing) Since StarRocks v3.2, you can avoid the 307 redirect and the associated Docker networking complexity (where FE redirects to an internal container IP that your host cannot reach) by enabling the FE's built-in proxying feature. Instead of deploying a separate Nginx proxy, you can configure the FE itself to proxy the Stream Load data to the BE: * Parameter:
enable_fe_proxy
* How to use: 1. Pass this as an environment variable when starting the container:
Copy code
bash
        docker run -p 9030:9030 -p 8030:8030 -e FE_CONF_enable_fe_proxy=true starrocks/allin1-ubuntu
2. Or, connect via MySQL and set it globally (if supported for that version):
Copy code
sql
        ADMIN SET FRONTEND CONFIG ("enable_fe_proxy" = "true");
When this is enabled, you can send Stream Load requests directly to the FE HTTP port (8030) without being redirected to the BE's internal IP. 3. Using FQDN as an Alternative If you prefer not to use the proxy, you can avoid redirect issues by: * Starting the container with a specific hostname (e.g.,
--hostname starrocks-allin1
). * Mapping that hostname to
127.0.0.1
in your host's
/etc/hosts
file. * The FE will then redirect to
starrocks-allin1:8040
, which your host can resolve and reach (provided you exposed port 8040). Summary of Ports Service | Default Port | Description FE MySQL | 9030 | Client connections FE HTTP | 8030 | Stream Load entry point / Web UI BE HTTP | 8040 | Data processing (target of 307 redirect) FE Proxy | 8080 | (Optional) Separate component for proxying redirects Referencesadministration/management/FE_configuration.mdquick_start/helm.md