Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use my custom modules out of the box (branch 17.0) #160

Open
Damien-VS opened this issue Sep 15, 2024 · 0 comments
Open

Can't use my custom modules out of the box (branch 17.0) #160

Damien-VS opened this issue Sep 15, 2024 · 0 comments

Comments

@Damien-VS
Copy link

Damien-VS commented Sep 15, 2024

context

encountered in 17.0
not tested on other branches

bug description

When building the hosted docker image

docker build -f "Dockerfile" -t dockerdoo:latest "."

The custom folder copy fails to do anything, executing with this command

#20 [production  8/13] COPY --chown=odoo:odoo ./custom /mnt/extra-addons

This is because the custom/* is in the .dockerignore file

expected

  • I place a module in the ./custom directory
  • I build & run the docker image through docker compose up -d
  • the module is accessible in my odoo instance

fix proposal

  • remove custom/* from .dockerignore
  • explain why this behaviour is wanted in the README.md with a workaround / correct way to achieve the expected behaviour

🙏 Thanks

@Damien-VS Damien-VS changed the title Can't use my custom modules out of the box Can't use my custom modules out of the box (branch 17.0) Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant