Describe the bug
Multiple containers can have the same created_at timestamp, meaning sorting will result in different results
To Reproduce
Steps to reproduce the behavior:
use a docker-compose to create multiple containers at the same time
sort by any column 3 times, when reset, order might not be the same as the start
Expected behavior
When no SortedOrder is set, containers should be sorted by a consistent behaviour
Additional context
Should try to create a unique created_at, could append something, such as the hashed name/image/id, to the created at, to make unique, sortable, value
Describe the bug Multiple containers can have the same created_at timestamp, meaning sorting will result in different results
To Reproduce Steps to reproduce the behavior:
Expected behavior When no SortedOrder is set, containers should be sorted by a consistent behaviour
Additional context Should try to create a unique created_at, could append something, such as the hashed name/image/id, to the created at, to make unique, sortable, value