Describe the bug
I am using Orbstack as a drop-in replacement for Docker Desktop on macOS, specifically for use with Dev Containers in Visual Studio Code.
I am trying to run my Svelte application, which binds to http://localhost:5173/ within the container.
With Docker Desktop, this works right out of the box. See my Dev containers setup:
{
"name": "Node",
"dockerFile": "Dockerfile",
"customizations": {
"vscode": {
"settings": {},
"extensions": [
"svelte.svelte-vscode",
"bradlc.vscode-tailwindcss"
]
}
}
}
(The dockerfile is just FROM node:20)
Once I run my app inside of the container, it will be available on the host at localhost:5173
However, this is not the case with Orbstack. Running this same configuration using Orbstack will result in the app not being available.
Only when I make my app listen on 0.0.0.0, will it be available on the host.
To Reproduce
No response
Expected behavior
I would expect the application to be available without having to bind to 0.0.0.0, just like with Docker Desktop
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.7.2
Commit: 50f93373f351fe839fd72948e6aad032774c0f6c (v1.7.2)
System info:
macOS: 15.0 (24A335)
CPU: arm64, 12 cores
CPU model: Apple M3 Pro
Model: Mac15,6
Memory: 36 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-10-03T14-24-35.360945Z.zip
Screenshots and additional context (optional)
No response
Describe the bug
I am using Orbstack as a drop-in replacement for Docker Desktop on macOS, specifically for use with Dev Containers in Visual Studio Code.
I am trying to run my Svelte application, which binds to http://localhost:5173/ within the container.
With Docker Desktop, this works right out of the box. See my Dev containers setup:
{ "name": "Node", "dockerFile": "Dockerfile", "customizations": { "vscode": { "settings": {}, "extensions": [ "svelte.svelte-vscode", "bradlc.vscode-tailwindcss" ] } } }(The dockerfile is just
FROM node:20)Once I run my app inside of the container, it will be available on the host at localhost:5173
However, this is not the case with Orbstack. Running this same configuration using Orbstack will result in the app not being available.
Only when I make my app listen on
0.0.0.0, will it be available on the host.To Reproduce
No response
Expected behavior
I would expect the application to be available without having to bind to 0.0.0.0, just like with Docker Desktop
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.7.2
Commit: 50f93373f351fe839fd72948e6aad032774c0f6c (v1.7.2)
System info:
macOS: 15.0 (24A335)
CPU: arm64, 12 cores
CPU model: Apple M3 Pro
Model: Mac15,6
Memory: 36 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-10-03T14-24-35.360945Z.zip
Screenshots and additional context (optional)
No response