Odoo/docker documentation on Docker Hub missing critical step for simple example - style sheets missing is common result
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 1.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
The base example in the odoo docker docs is missing a required step:
Start a PostgreSQL server
$ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:10
Start an Odoo instance
$ docker run -p 8069:8069 --name odoo --link db:db -t odoo
Should be
Start a PostgreSQL server
$ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:10
Create a volume for web data
$ docker create odoo-web-data
Start an Odoo instance
$ docker run -p 8069:8069 --name odoo -v odoo-web-data:/var/lib/odoo --link db:db -t odoo
Running the single image version of odoo without a volume for web data will lose stylesheets any other content in the filestore that is generated at initial DB creation and bootstrap if the container is removed cleaned up.
The fix is simple- add a step to create the odoo-web-data volume, and then mounting it to the docker run command.
When the volume is not present, a recycling of the odoo image will lose filestore data, and stylesheets will 404 when the frontend tries to retrieve them.
Contributor guide
No contributing guide indexed for this repository
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
Start with the Docker Hub base example described in the issue and compare its PostgreSQL and Odoo commands with the proposed version. Done means the example creates the odoo-web-data volume and mounts it at /var/lib/odoo so filestore data and stylesheets persist when the Odoo container is recycled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100