Welcome @Sudipta_Talukder
Yes, we are looking into the issue with the updated job container for the default version of Snippy.
The current workaround is to fall back to using a prior version that is not impacted: Snippy 4.4.5+galaxy2
That uses a slightly different software stack. To be clear: the memory allocated is probably not really 0 MB but should be based on the job container resources. The resources will never be less than 1 MB, which is still not enough! This is what we are investigating.
The other option is to try at a different server such as UseGalaxy.eu or UseGalaxy.org.au for now. Moving data between servers is easy and encouraged! 
This was uncovered late last week. I’ll follow up more and link a ticket if one is needed. Thank you for reporting the issue here and our apologies for the current troubles!