You want to represent docker containers and how they deploy your data grids. But you also want to show how this is related to your software architecture.
I think you should first have a look a deployment diagrams. These are best suited for representing the execution of your system across hardware and software environments:
- here an example showing how to represent docker hosts, and images with "nodes" and communication paths
- here an example showing how to further represent the inside of a node with "artifacts" such as for example components, which could represent your data-grid components linked across several nodes, and message queue if it's an independent component.
- here a nice overview of the notation. Interesting in your case: you could also show the deployment of a artifact accross several nodes with a dependency arrow to the nodes. This would make the diagram focusing on how your components are distributed, keeping artifacts on one side and execution environment on the other, avoid over-inflated 3D node boxes.
The component architecture could then be described in a component diagram, as pointed out by Thomas Kilian in his comment. For the sake of completeness: see here or here.
Finally, you could explain the relationship between your high-level independent components and your detailed classes by using the composite structure diagram.
