increased docker shared memory for nightly test

[roywei]

Description

This is a potential fix for #14026
need to be tested on CI docker environment before merge.

Suggest to disable the test first #14120

according to #11872
Gluon data loader will hang and give connection refused error if shared memory is too small. Our nightly test on tutorials give 500m shared memory on docker now. Increasing it to 1500m.

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[jlcontreras]

Lgtm

[vandanavk]

@mxnet-label-bot add [pr-awaiting-review, Gluon]

@roywei could you add "Fixes #14026" in the PR description? This will automatically close the issue when the PR is merged.

[vandanavk]

@mxnet-label-bot update [pr-work-in-progress, Gluon]

[marcoabreu]

Is there an open ticket to improve the error message?