[Feature]: Docker / Docker Compose Instructions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, docker-compose
- Domain
- documentation
Research direction
Start by locating the existing Docker Desktop installation instructions in the documentation and review how installation options are organized. Add instructions for regular Docker and Docker Compose alongside the existing guidance; the work is done when Linux users can follow either supported approach without relying on Docker Desktop.
Written by the indexing model from the issue text.
Description
Is there an existing feature request for this?
- I have searched existing issues and feature requests, and this is not a duplicate.
Problem or Use Case
There are instructions on how to install with Docker Desktop. In Linux though, most won't want to install that.
You could put instructions on how to install with regular Docker, and/or with Docker Compose. I think that's a much better approach of installing it.
Proposed Solution
Add Docker / Docker Compose installation instructions besides Docker Desktop.
Alternatives Considered
No response
Priority / Severity
Medium - Would improve experience
Estimated Scope
Small - UI tweak, config option, or minor change
Feature Area
Documentation
Technical Implementation Ideas (Optional)
No response
Additional Context
No response
- Dominant language
- MDX
- Stars
- 14
- Forks
- 61
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 46
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 OpenHands/docs
-
Docker execution docs use incorrect env var names (OH_EXECUTION_* instead of OH_CONVERSATION_*)Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Moonshot provider documentation references a deprecated model, setup fails per doc recommendationsOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Document software factory setup through Agent Canvas UIPossibly taken @neubig claimed this 18 days ago. Openenhancement ready-for-dev
OpenHands/docs#796 · 1 assignee ·
Maintainers usually reply within 1 day
-
Document SDK-owned browser conversation event streamsPossibly taken @neubig claimed this 18 days ago. Open
OpenHands/docs#794 · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
copilot documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
skill:code-review
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day