Proxies

wasmCloud pulls images for components and providers from OCI (Open Container Initiative) registries. Additionally, the wash up utility pulls release binaries for nats-server, wadm, and wasmcloud from GitHub. Both of these are done over HTTPS and can be done through a proxy.

info

This proxy configuration should be set when running wash up or when running the wasmCloud host.

Proxy configuration

wash will respect the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables (and their lowercase equivalents) by passing them directly down to our HTTP libraries. If you are using a proxy, you can set these variables to the appropriate values. For example:

Unix

shell

export HTTP_PROXY=http://proxy.example.com:8080
export HTTPS_PROXY=https://proxy.example.com:8080
wash up

Powershell

powershell

$env:HTTP_PROXY = "http://proxy.example.com:8080"
$env:HTTPS_PROXY = "https://proxy.example.com:8080"
wash up

Proxy authentication

If your proxy requires authentication, you can set the WASH_PROXY_USERNAME and WASH_PROXY_PASSWORD environment variables. For example:

Unix

shell

export WASH_PROXY_USERNAME='myuser'
export WASH_PROXY_PASSWORD='myp4$$w0rd'
wash up

It's recommended to use single quotes to avoid issues with special characters in the password.

Powershell

powershell

$env:WASH_PROXY_USERNAME = "myuser"
$env:WASH_PROXY_PASSWORD = "myp4$$w0rd"
wash up

This configuration will allow wash to download binaries through the proxy. For authenticating to private registries, see the Registries guide.