I have done the following

• I have searched the existing issues
• If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

Steps to Reproduce

1. brew install container (on a clean system)
2. container system start
3. Observe: apiserver crashes in a loop with "cannot find any plugins with type network"

Workaround

Two symlinks and a config.toml are needed post-install:

mkdir -p "${BREW_PREFIX}/libexec/container"
ln -sf "${BREW_PREFIX}/opt/container/libexec/container-plugins" \
       "${BREW_PREFIX}/libexec/container/plugins"
ln -sf "${BREW_PREFIX}/opt/container/libexec/container-plugins" \
       "${BREW_PREFIX}/libexec/container-plugins"

mkdir -p "$HOME/Library/Application Support/com.apple.container/config"
cat > "$HOME/Library/Application Support/com.apple.container/config/config.toml" <<EOF
install-root = "${BREW_PREFIX}"
EOF

Problem description

Description

When installing container 1.0.0 via brew install container, the apiserver
fails immediately with:

cannot find any plugins with type network

This makes the tool completely non-functional after a standard brew install.

Root Cause

The apiserver derives install-root from the brew prefix (e.g. /opt/homebrew
or ~/.brew) and looks for plugins at:

{brew-prefix}/libexec/container/plugins/

But the Homebrew formula installs plugins to:

{brew-prefix}/Cellar/container/1.0.0/libexec/container-plugins/

which is symlinked via opt to:

{brew-prefix}/opt/container/libexec/container-plugins/

Neither of these matches the path the apiserver expects. No config.toml is
written by the formula to tell the apiserver where to find its plugins.

Expected Behaviour

brew install container && container system start should work out of the box.
The formula's post_install block should create these symlinks or write the
config.toml correctly.

Environment

## Environment

- macOS 26 (Tahoe)
- Apple Silicon
- container 1.0.0 via Homebrew formula
- Reproducible with both system-wide (/opt/homebrew) and user-local (~/.brew) 
  Homebrew installations

Code of Conduct

• I agree to follow this project's Code of Conduct