4 ms·

Why’s it not on Linux? What are the difficulties with that platform?

by kwakubiney 2mo ago

cogman10 2mo ago
Looks like they do support Ubuntu. Is this open source? Can I install this on a non Ubuntu system?
- aborsy 2mo ago
  A limited form of it with different syntax comes with Docker Desktop. The sbx tool is not available for non-Ubuntu distributions.
- rocfan 2mo ago
  CLI works on Fedora. Been using it daily for ~ a week. See repo `docker/sbx-releases`. The `.rpm` there has Rocky Linux in the name but works on Fedora.
srini-docker 2mo ago
Linux is available today (Ubuntu): github.com/docker/sbx-releases. Our webpage showing only brew and winget is on us. For the people upthread who asked about on customization: templates (like snapshotting a running sandbox) and kits (YAML applied at creation like install steps, files, network and credential rules, or define a new agent outright) are the supported path now. It's early but take a look here: https://docs.docker.com/ai/sandboxes/customize/ https://docs.docker.com/ai/sandboxes/customize/ On MCP, since credential handling was mentioned here: the sandbox sees one gateway endpoint, and OAuth tokens stay in the host credential store rather than in the VM. https://docs.docker.com/ai/sandboxes/mcp-gateway/ https://docs.docker.com/ai/sandboxes/mcp-gateway/ All this is early. We're looking at more based on feedback from users like running sandboxes in the background for long-horizon work and a lot more (including what you all raised in the thread here). Keep them coming.
- tacker2000 2mo ago
  Please consider adding MacPorts support. Brew is notoriously developer-unfriendly.
  - dallen33 2mo ago
    How so?
    - bmurphy1976 2mo ago
      The parent didn't go into any detail. I can. Homebrew has a history of ripping out your foundation underneath you. One day you are on Python 3.8, then next day you are on Python 3.10 and all your packages are broken. MacPorts doesn't do that. Now, whether you should you be using the Homebrew Python is a completely different question. YMMV for other platforms managed via Homebrew. I've traditionally used MacPorts for dev tooling and Homebrew for everything else, but with more aggressive adoption of tooling like uv an nvm I'm not sure the different really matters for me anymore.
      - xrisk 2mo ago
        pyenv has been standard tooling for far longer than uv. depending on package manager supplied Python packages only makes sense if you’re running rhel or Debian or something and your application is packaged/deployed/the maintenance path uses dnf/apt. Otherwise you should always use a venv and use an out of package manager update mechanism. Like, in a broader sense, vendoring dependencies only makes sense if you’re shipping an application, not on a dev box.
        tacker2000 2mo ago
        This is not about python packages, this is about python itself.
        stavros 2mo ago
        That's what the GP means as well, you can use pyenv and uv to install multiple versions of Python and create envs with whichever version you want to use.
- srini-docker 2mo ago
  Quick update: webpage reflects Linux support as well, thanks for the flag. https://www.docker.com/products/docker-sandboxes/ https://www.docker.com/products/docker-sandboxes/

Why’s it not on Linux? What are the difficulties with that platform?

cogman10 2mo ago

Looks like they do support Ubuntu. Is this open source? Can I install this on a non Ubuntu system?

aborsy 2mo ago
A limited form of it with different syntax comes with Docker Desktop. The sbx tool is not available for non-Ubuntu distributions.
rocfan 2mo ago
CLI works on Fedora. Been using it daily for ~ a week. See repo `docker/sbx-releases`. The `.rpm` there has Rocky Linux in the name but works on Fedora.

srini-docker 2mo ago

Linux is available today (Ubuntu): github.com/docker/sbx-releases. Our webpage showing only brew and winget is on us. For the people upthread who asked about on customization: templates (like snapshotting a running sandbox) and kits (YAML applied at creation like install steps, files, network and credential rules, or define a new agent outright) are the supported path now. It's early but take a look here: https://docs.docker.com/ai/sandboxes/customize/ https://docs.docker.com/ai/sandboxes/customize/ On MCP, since credential handling was mentioned here: the sandbox sees one gateway endpoint, and OAuth tokens stay in the host credential store rather than in the VM. https://docs.docker.com/ai/sandboxes/mcp-gateway/ https://docs.docker.com/ai/sandboxes/mcp-gateway/ All this is early. We're looking at more based on feedback from users like running sandboxes in the background for long-horizon work and a lot more (including what you all raised in the thread here). Keep them coming.

tacker2000 2mo ago
Please consider adding MacPorts support. Brew is notoriously developer-unfriendly.
- dallen33 2mo ago
  How so?
  - bmurphy1976 2mo ago
    The parent didn't go into any detail. I can. Homebrew has a history of ripping out your foundation underneath you. One day you are on Python 3.8, then next day you are on Python 3.10 and all your packages are broken. MacPorts doesn't do that. Now, whether you should you be using the Homebrew Python is a completely different question. YMMV for other platforms managed via Homebrew. I've traditionally used MacPorts for dev tooling and Homebrew for everything else, but with more aggressive adoption of tooling like uv an nvm I'm not sure the different really matters for me anymore.
    - xrisk 2mo ago
      pyenv has been standard tooling for far longer than uv. depending on package manager supplied Python packages only makes sense if you’re running rhel or Debian or something and your application is packaged/deployed/the maintenance path uses dnf/apt. Otherwise you should always use a venv and use an out of package manager update mechanism. Like, in a broader sense, vendoring dependencies only makes sense if you’re shipping an application, not on a dev box.
      - tacker2000 2mo ago
        This is not about python packages, this is about python itself.
        stavros 2mo ago
        That's what the GP means as well, you can use pyenv and uv to install multiple versions of Python and create envs with whichever version you want to use.
srini-docker 2mo ago
Quick update: webpage reflects Linux support as well, thanks for the flag. https://www.docker.com/products/docker-sandboxes/ https://www.docker.com/products/docker-sandboxes/