nextcloud / nextcloud/nextcloud-docker-dev
Linux Manjaro support
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
Hi,
When I tried to install the developer environment on my (arch-based) Linux Manjaro system, I encountered a few problems. I'm assuming one of these problems will be relevant for other Linux Manjaro users.
The installation process adds a series of {...}.local entries to /etc/hosts, but these entries are initially ignored on my system (and other systemd-based Linux systems).
In cat /etc/nsswitch.conf I have the following line:
hosts: mymachines mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] files myhostname dns
Because mdns_minimal [NOTFOUND=return] is listed before files, the .local addresses in /etc/hosts are ignored. The suffix .local is special and is reserved for mDNS (multicast DNS). See also https://en.wikipedia.org/wiki/Special-use_domain_name
Suggested workaround: rename .local to .test everywhere (/etc/hosts, project .env, project docker-compose.yml) and do a fresh install.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the installation process that writes entries to /etc/hosts, then inspect the project .env and docker-compose.yml files mentioned in the issue. Reproduce a fresh installation on Linux Manjaro and verify that the development environment resolves its hostnames correctly without relying on .local.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, linux
- Domain
- devops, networking, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100