FastGPT administrators managing self-hosted AI agent platforms face mandatory infrastructure updates following the release of version 4.16.0. The new guidance forces a transition away from deprecated E2B configurations and requires specific image tag alignment to ensure stability across the sandbox proxy and associated service components.
The update requires deployments to refresh the Agent-sandbox-proxy service, with new configuration options for PORT and PREVIEW_PORT introduced to handle traffic separation for gateways lacking unified support. Connectivity validation is now managed through the /health endpoint. Component image tags have been standardized: fastgpt-app and fastgpt-pro must be updated to version 4.16.0, while fastgpt-plugin, agent-sandbox-volume, and agent-sandbox-proxy require version 0.3.0.
Administrators must carefully audit environment variables, as the transition includes a name change for volume prefixes. Current documentation identifies the variable as AGENT_SANDBOX_OPENSANDBOX_VOLUME_NAME_PREFIX, replacing previous naming conventions. Users still utilizing E2B must migrate to opensandbox or sealosdevbox providers and purge the AGENT_SANDBOX_E2B_API_KEY to prevent conflicts.
Beyond mandatory migrations, the platform introduces granular control over resource allocation. New variables allow for the adjustment of CPU counts, memory limits, storage capacity, and automated suspension or archival intervals. While the system allows for flexible tuning, mixed-version deployments are strictly unsupported. Security remains a primary concern; although the platform does not enforce cross-origin isolation by default, developers are advised to implement it to mitigate potential vulnerabilities in sandbox proxy deployments.
Comments (0)
No comments yet. Be the first!