How to use odoo:17 image in devcontainer?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, dockerfile
- Domain
- devops, documentation
Research direction
Start with .devcontainer/Dockerfile.fajnodoo17 and .devcontainer/devcontainer.json, then compare them with the odoo:17 image overview. Investigate the image's user setup, installed module locations, and how odoo-bin is invoked. Done means documenting verified devcontainer usage and recommendations in the odoo:17 image overview.
Written by the indexing model from the issue text.
Description
I am trying to create a devcontainer for the development of custom Odoo modules. This devcontainer is based on the official odoo:17 image. You can see the current state of my devcontainer in my-odoo-project.zip. I would like to ask the following questions:
-
It took me a few days of effort to discover that I needed to add a new user with UID/GID 1000 in the
odoo:17image to make the devcontainer work with this image. See the creation of thedeveloperuser in.devcontainer/Dockerfile.fajnodoo17and the"remoteUser"in.devcontainer/devcontainer.json. Here are my questions:- Is creating a user with UID/GID 1000 the only solution, or is there a more straightforward alternative?
- If user creation is the correct approach, is it possible to pre-create such a devcontainer-friendly user in the Docker image to make it easily usable for a devcontainer creation? Or at least, is it possible to add a section "How to use this image in a devcontainer" in the
odoo:17image overview describing how to extend the image by user creation?
-
How can I map the installed Odoo modules (applications) to my devcontainer? Where are they located in the
odoo:17image? -
How can I run
odoo-bincommand in the devcontainer (or Docker container)? -
Do you have any other recommendations on how to correctly use the
odoo:17image in a devcontainer for development? Would it be possible to include these recommendations in theodoo:17image overview?
- Dominant language
- Dockerfile
- Stars
- 1.2k
- Forks
- 1.7k
- 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
- 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 odoo/docker
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
Missing PyJWT ?Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
ci-red code-regression gfx942 platform: Linux platform: Windows post-merge project: hipblaslt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ROCm/rocm-libraries#16354 ·
Maintainers usually reply within 2 days
-
area:plugins kind:perf priority:p3 ready
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Auto-Format Suggestions job fails at setup: reviewdog/action-suggester v1.27.0 uses an action pinned by tagPossibly taken @fgogolli claimed this today. Openarea: ci priority: p2 size: S type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
finos/open-resource-broker#883 ·
Maintainers usually reply within 1 day
-
status/to triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day