zed-industries/zed · error
Not currently supported for docker_exec
Error message
Not currently supported for docker_exec
What it means
In DockerRemoteConnection::build_forward_ports_command: port forwarding is not implemented for docker-exec connections (docker exec provides no port-forward mechanism), so the call unconditionally returns this error.
Source
Thrown at crates/remote/src/transport/docker.rs:849
match interactive {
Interactive::Yes => docker_args.push("-it".to_string()),
Interactive::No => docker_args.push("-i".to_string()),
}
docker_args.push(self.connection_options.container_id.to_string());
docker_args.append(&mut inner_program);
Ok(CommandTemplate {
program: self.docker_cli().to_string(),
args: docker_args,
// Docker-exec pipes in environment via the "-e" argument
env: Default::default(),
})
}
fn build_forward_ports_command(
&self,
_forwards: Vec<(u16, String, u16)>,
) -> Result<CommandTemplate> {
Err(anyhow::anyhow!("Not currently supported for docker_exec"))
}
fn connection_options(&self) -> RemoteConnectionOptions {
RemoteConnectionOptions::Docker(self.connection_options.clone())
}
fn path_style(&self) -> PathStyle {
self.path_style.unwrap_or(PathStyle::Unix)
}
fn remote_platform(&self) -> RemotePlatform {
// Docker containers are always Linux; the platform is populated during
// setup, so this fallback is only for the brief pre-detection window.
self.remote_platform.unwrap_or(RemotePlatform {
os: RemoteOs::Linux,
arch: RemoteArch::X86_64,View on GitHub (pinned to 5a9b9558db)
Solutions
- Use a full dev container (docker) connection instead of docker exec
- Forward ports manually via docker CLI
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at crates/remote/src/transport/docker.rs:846 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@5a9b9558db (2026-08-20).
Data as JSON: /api/errors/fe37bb758ff804ff.
Report an issue: GitHub.