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

Error while setting up BigBlueButton 2.7 Docker: "unable to stat C, error: stat C: no such file or directory

Open
#305 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, shell
Domain
devops

Research direction

Start with the ./scripts/setup entry point in the BigBlueButton docker repository and reproduce the setup using the reported answers. Trace where the "unable to stat C" message is produced and identify the input or path that causes it; done means the setup completes successfully or the required environment and remediation are documented.

Written by the indexing model from the issue text.

Description

I cloned the BigBlueButton 2.7 Docker repository from GitHub (https://github.com/bigbluebutton/docker) and ran the command ./scripts/setup. During the setup process, I was prompted with some questions, which I answered. However, at the end of the setup, I encountered the following error:

2023/11/24 10:27:30 unable to stat C, error: stat C: no such file or directory

I have attempted to debug and resolve the issue, but I couldn't find a solution. It seems to be related to a file or directory named "C," but I am unsure about the cause and how to address it.

I am seeking guidance on resolving the "unable to stat C" error during the setup of BigBlueButton 2.7 Docker version. Any insights into the cause of the issue and potential solutions would be greatly appreciated.

Dominant language
Shell
Stars
436
Forks
275
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 bigbluebutton/docker

All issues in bigbluebutton/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.