Skip to content

Commit 4d49389

Browse files
authored
Screenshot and port updates (#2163)
* Update couchbase screenshots * Update ports * Update ports * Update ports * Remove ports, point at docs * Add current client-node ports * Add client->node ports to run commands
1 parent fa2f47d commit 4d49389

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

couchbase/content.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,24 +22,26 @@ Here is how to get a single node Couchbase Server cluster running on Docker cont
2222

2323
**Step - 1 :** Run Couchbase Server docker container
2424

25-
`docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase`
25+
`docker run -d --name db -p 8091-8097:8091-8097 -p 11210:11210 -p 11207:11207 -p 18091-18095:18091-18095 -p 18096:18096 -p 18097:18097 couchbase`
26+
27+
Note: Couchbase Server can require a variety of ports to be exposed depending on the usage scenario. Please see https://docs.couchbase.com/server/current/install/install-ports.html for further information.
2628

2729
**Step - 2 :** Next, visit `http://localhost:8091` on the host machine to see the Web Console to start Couchbase Server setup.
2830

29-
![Setup splash screen](https://d774lla4im6mk.cloudfront.net/6.6.2/setup-initial.jpg)
31+
![Setup splash screen](https://d774lla4im6mk.cloudfront.net/setup-initial.jpg)
3032

3133
Walk through the Setup wizard and accept the default values.
3234

3335
- Note: You may need to lower the RAM allocated to various services to fit within the bounds of the resource of the containers.
3436
- Enable the beer-sample bucket to load some sample data.
3537

36-
![Creating a cluster](https://d774lla4im6mk.cloudfront.net/6.6.2/cluster-creation.jpg)
38+
![Creating a cluster](https://d774lla4im6mk.cloudfront.net/cluster-creation.jpg)
3739

38-
![Completing the wizard](https://d774lla4im6mk.cloudfront.net/6.6.2/finish-wizard.jpg)
40+
![Completing the wizard](https://d774lla4im6mk.cloudfront.net/finish-wizard.jpg)
3941

40-
![UI home](https://d774lla4im6mk.cloudfront.net/6.6.2/ui-home.jpg)
42+
![UI home](https://d774lla4im6mk.cloudfront.net/ui-home.jpg)
4143

42-
![Loading sample data](https://d774lla4im6mk.cloudfront.net/6.6.2/load-sample-data.jpg)
44+
![Loading sample data](https://d774lla4im6mk.cloudfront.net/load-sample-data.jpg)
4345

4446
**Note :** For detailed information on configuring the Server, see [Deployment Guidelines](https://docs.couchbase.com/server/current/install/install-production-deployment.html).
4547

@@ -97,11 +99,11 @@ These ulimit settings are necessary when running under heavy load. If you are ju
9799

98100
To set the ulimits in your container, you will need to run Couchbase Docker containers with the following additional `--ulimit` flags:
99101

100-
`docker run -d --ulimit nofile=40960:40960 --ulimit core=100000000:100000000 --ulimit memlock=100000000:100000000 --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase`
102+
`docker run -d --ulimit nofile=40960:40960 --ulimit core=100000000:100000000 --ulimit memlock=100000000:100000000 --name db -p 8091-8097:8091-8097 -p 11210:11210 -p 11207:11207 -p 18091-18095:18091-18095 -p 18096:18096 -p 18097:18097 couchbase`
101103

102104
Since "unlimited" is not supported as a value, it sets the core and memlock values to 100 GB. If your system has more than 100 GB RAM, you will want to increase this value to match the available RAM on the system.
103105

104-
Note:The `--ulimit` flags only work on Docker 1.6 or later.
106+
Note: The `--ulimit` flags only work on Docker 1.6 or later.
105107

106108
**Network Configuration and Ports :** Couchbase Server communicates on many different ports (see the [Couchbase Server documentation](https://docs.couchbase.com/server/current/install/install-ports.html#ports-listed-by-communication-path)). Also, it is generally not supported that the cluster nodes be placed behind any NAT. For these reasons, Docker's default networking configuration is not ideally suited to Couchbase Server deployments. For production deployments it is recommended to use `--net=host` setting to avoid performance and reliability issues.
107109

0 commit comments

Comments
 (0)