In the Docker image we have the app now living in /app, but we also have the installed modules in /app/local. This seems to cause conflicts with mounting a local metacpan-web in /app as it immediately throws:
web-1 | Error while loading /app/app.psgi: Can't locate Config/ZOMG.pm in @INC (you may need to install the Config::ZOMG module) (@INC contains: /app/local/lib/perl5 /usr/local/lib/perl5/site_perl/5.36.3/x86_64-linux-gnu /usr/local/lib/perl5/site_perl/5.36.3 /usr/local/lib/perl5/vendor_perl/5.36.3
/x86_64-linux-gnu /usr/local/lib/perl5/vendor_perl/5.36.3 /usr/local/lib/perl5/5.36.3/x86_64-linux-gnu /usr/local/lib/perl5/5.36.3) at /app/app.psgi line 11.
web-1 | BEGIN failed--compilation aborted at /app/app.psgi line 11.
web-1 | unable to find PSGI function entry point.
web-1 | no app loaded. GAME OVER
This was not obvious until now because the docker-compose config is set up as:
In the Docker image we have the app now living in
/app
, but we also have the installed modules in/app/local
. This seems to cause conflicts with mounting a localmetacpan-web
in/app
as it immediately throws:This was not obvious until now because the
docker-compose
config is set up as:which means that with the current setup, changes to the local env won't be reflected in the running Docker container.