Skip to content
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

Try-Us-Out instructions should not use Docker, but binaries #44

Closed
andreimatei opened this issue Feb 11, 2016 · 2 comments
Closed

Try-Us-Out instructions should not use Docker, but binaries #44

andreimatei opened this issue Feb 11, 2016 · 2 comments

Comments

@andreimatei
Copy link
Contributor

You can't access http:\\<docker ip>:26527 because docker ports/networking something something. I think we need more to the docker invocation than what's documented here. I think @tschottdorf would know.

Also we need to figure out the relationship between the installation instructions we have in the README.md and the docs site.

@tbg
Copy link
Member

tbg commented Feb 11, 2016

I think we should start exposing our linux nightlies and the brew formula (assuming it works fairly reliably). We can keep the Docker stuff around somewhere, but maybe not at the top.

I'll fix up the README invocation. Should be passing a flag or two, but on OSX there's always some loss of simplicity because of the VM.

@tbg tbg changed the title instructions for docker setup on OSX don't make the UI accessible (port 26527) Try-Us-Out instructions should not use Docker, but binaries Feb 11, 2016
@jseldess
Copy link
Contributor

Fixed with readme updates: cockroachdb/cockroach#5511. We're now just linking to our install page in the docs.

Simran-B added a commit to Simran-B/docs that referenced this issue Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants