docker-galaxy-stable
docker-galaxy-stable copied to clipboard
bgruening
[compose] /export/venv should be part of galaxy-web and not galaxy-init
Starting the compose setup on virtualised file system can take easily 10 minutes, a lot in part due to the needed copies from the init container to the shared filesystem. In an environment where all tool's load is run in containers outside of galaxy-web, I don't think that there is a need to have anymore venv on the init container and have it copied to the shared file system, it could well be directly on the galaxy-web container, avoiding that delay (the venv is probably the largest component to be copied, possibly with plenty of small files).
I think init is a good place to put branding and a number of other things that are unique to each instance that are difficult to inject via configuration, but should be leaner.
On Thu, 6 Jun 2019, 18:44 Björn Grüning, [email protected] wrote:
galaxy-init will die with 19.05 hopefully ...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bgruening/docker-galaxy-stable/issues/511?email_source=notifications&email_token=AACZ6XSBGECPX7J2OTFXHE3PZFEIPA5CNFSM4HVFPVI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDT7JI#issuecomment-499597221, or mute the thread https://github.com/notifications/unsubscribe-auth/AACZ6XSYOSQX3Y4UQ2RHR73PZFEIPANCNFSM4HVFPVIQ .
...but that could as well happen by doing FROM the galaxy-web container I guess and putting stuff there.