[21.01] add GALAXY_MEMORY_MB* to passt hrough

[bgruening]

What did you do?

Its passes "GALAXY_MEMORY_MB" and "GALAXY_MEMORY_MB_PER_SLOT" inside containers. Currently only GALAXY_SLOTS, HOME and a few TEMP dirs are passed through.

Why did you make this change?

I found container tools that did not use the specified GALAXY_SLOTS.

How to test the changes?

Run a Docker enabled Tool and check if GALAXY_MEMORY_MB is set via the -e variables.

License

• I agree to license these contributions under Galaxy's current license.
• I agree to allow the Galaxy committers to license these and all my past contributions to the core galaxy codebase under the MIT license. If this condition is an issue, uncheck and just let us know why with an e-mail to galaxy-committers@lists.galaxyproject.org.

[bgruening]

@natefoo that might be interesting for you.

[natefoo]

We probably ought to actually set those limits on the container directly as well, but this is definitely a good move. Thanks @bgruening!

[bgruening]

We probably ought to actually set those limits on the container directly as well, but this is definitely a good move.

Yes we should. I seem container escape our general cgroup monitoring otherwise. I saw jobs reporting only 1GB max-memory usage, but they used in the Docker processes much more.

[github-actions]

This PR was merged without a "kind/" label, please correct.