-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uplink from host to storagenode containers doesn't work on windows #37
Comments
From an internal discussion:
|
Another option discussed is only to support WSL and not fix this for native windows. We need to decide how we would like to proceed. |
@dlamarmorgan can you verify if this ticket was actually solved and we can close it? Or if this is something we need to do still. Thank you! |
This issue has not been fully resolved, though we do have a workaround now that uses docker exec to run in an uplink specific container. A more complex host config could still be a better native solution, but I don't know how much effort that would take. Personally I think we should keep this ticket open, because we still can't use storj-up to test a windows uplink binary. However, if we complete https://github.com/storj/team-delivery/issues/294 then we may have no need for this ticket anymore. |
Noting for posterity (and because I keep forgetting) this also applies to running storj-up on macOS, not just Windows. |
Due to the docker desktop limitation on windows
Docker Desktop can’t route traffic to Linux containers.
uplink fails when it is used from a windows host to a linux container.
The object browser in the satellite GUI does seem to work ok, likely because it uses the gateway to send the data, which is exposed directly to the host via port mapping.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: