Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Looking for clarity on setting up couchdb single_node with docker-compose

Open
  • Is something wrong?
#247 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose
Domain
databases, devops

Research direction

Start with the repository README and the linked Dockerfile discussion, then compare the local.ini locations shown in the issue with the couchdb:2 image setup. Document whether single_node=true is supported for this image and the supported way to create _users, _replicator, and _global_changes; done means a clear, reproducible docker-compose setup.

Written by the indexing model from the issue text.

Description

Expected Behavior

I am trying to set up a single node instance of couchdb:2 using docker-compose. I understand from reading the README the limitation that the _users, _replicator and global_changes dbs need to be set up after installation. I tried adding the single_node=true config in a local.ini file and copying that to /opt/couchdb/etc/ and /opt/couchdb/etc/local.d in via Dockerfile. Neither of those approaches seem to work. According to this comment, this seems to be a valid approach.

Is it not a viable solution for couchdb:2?

FWIW: Here is the local.ini file from inside the container:

root@528ea27a75a7:/opt/couchdb/etc/# cat local.ini 
[couchdb]
single_node = true

[chttpd]
bind_address = any

[httpd]
bind_address = any

[couch_httpd_auth]
require_valid_user = true

[chttpd]
require_valid_user = true

If not, then I need to create the _users, _replicator and _global_changes dbs a different way. I see this comment in the same thread. Is this still the best approach?

Much appreciated.

Dominant language
Dockerfile
Stars
290
Forks
146
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/couchdb-docker

All issues in apache/couchdb-docker

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.