Inconsistency in Docker documentation for GDB
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation
Research direction
Start with the Docker installation wiki's “How to run the worldserver with gdb” section and compare its instructions with the current container setup after PR #22418. Update the guide so it no longer references the removed apps/startup-scripts/gdb.conf file, then verify that the documented Docker GDB procedure no longer fails because of that missing file.
Written by the indexing model from the issue text.
Description
After following the Docker documentation for enabling GDB inside Docker (under How to run the worldserver with gdb), Docker Compose fails during the build because gdb.conf is missing.
The current guide still instructs users to copy apps/startup-scripts/gdb.conf into the image and to start worldserver with gdb -x /azerothcore/gdb.conf, but this file is no longer available after #22418. As a result, following the documentation leads to a build error instead of a working GDB setup.
It would be good to update the Docker GDB instructions so they match the current container setup and no longer reference the removed gdb.conf file.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from azerothcore/azerothcore.github.io
-
[Feature] Allow page / link previews to match the module information and readiablity in the linkOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
azerothcore/azerothcore.github.io#180 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in azerothcore/azerothcore.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[quality] useFocusTrap's Shift+Tab wrap and non-Tab/non-Escape key arms are never driven end to endPossibly taken @hivecommons-hive claimed this today. Openagent/quality hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4220 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
JuliusBrussee/caveman#1189 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#738 ·
Maintainers usually reply within 1 day