sh: 1: ip: not found
Open
Nobody has claimed this yet.
0. Needs triage
bug
image
upstream
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Using nextcloud:31.0.7-fpm, I have when I click in system info in browser, then in the nextcloud server logs:
sh: 1: ip: not found
Indeed, I do not have ip in the container image.
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
Reproduce the report by opening System Info in a nextcloud:31.0.7-fpm container and inspect the resulting server log; no file or test is named. Done means the System Info action no longer emits sh: 1: ip: not found in the container log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100