Skip to content

gocker is very peculiar about the container binary and doesn't check PATH$ #8

Description

@katertier

I installed container per Homebrew:

➜ brew list container
/opt/homebrew/Cellar/container/0.12.3/bin/container
/opt/homebrew/Cellar/container/0.12.3/bin/container-apiserver
/opt/homebrew/Cellar/container/0.12.3/etc/bash_completion.d/container
/opt/homebrew/Cellar/container/0.12.3/homebrew.container.service
/opt/homebrew/Cellar/container/0.12.3/homebrew.mxcl.container.plist
/opt/homebrew/Cellar/container/0.12.3/libexec/container-plugins/ (6 files)
/opt/homebrew/Cellar/container/0.12.3/libexec/ensure-container-stopped.sh
/opt/homebrew/Cellar/container/0.12.3/sbom.spdx.json
/opt/homebrew/Cellar/container/0.12.3/share/fish/vendor_completions.d/container.fish
/opt/homebrew/Cellar/container/0.12.3/share/zsh/site-functions/_container

gocker is not happy with it and very adamant where container runtime has to be, despite being documented as being on Homebrew as well:

➜ gocker system
Error: apple container CLI not found at /usr/local/bin/container; run 'gocker setup' to install it

And the very first thing gocker setup does, is to download the binary to /user/local/bin which is slightly irritating since it requires sudo for setting it up as well as updating it. Both are not required for installation and update through Homebrew.

➜ gocker setup
Checking macOS version... macOS 26 OK
Checking architecture... arm64 OK
Checking Apple Container CLI... not found
Downloading Apple Container from GitHub releases...
Downloading container-0.12.3-installer-signed.pkg...
Installing Apple Container requires administrator privileges.
installer: Package name is container-2924574934
installer: Upgrading at base path /
installer: The upgrade was successful.
Apple Container installed successfully.

If I understand the code correctly, you do look for nerdctl in PATH$ on Linux and even have a (undocumented) configuration item (RuntimeBinary), but I'd appreciate to be able to allow future users to use it without an additional installation of container runtime or the need to conjure a crystal ball (or read the code) to find the config option.

Apart from that: great and very helpful piece of software, it helped me to free myself of docker (which seem to have a penchant to forget that it could access the same configured volumes just fine before I restarted the container).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions