AllowedContainers not working as expected

[GBHU753]

Describe the bug
I could not get the AllowedContainers option to work for user assigned in the UserIDs array

To Reproduce
Steps to reproduce the behavior:

1. Run docker ps --format "{{.Names}}" to get the name of the container
2. Add the name as a string to the AllowedContainers array

Expected behavior
I expected that when /list is ran by a user the container would show

Screenshots
N/A

Additional context
I also tried the containers ID this did not work either

[Assaro]

Odd. I will have to check that. Do the containers appear in the list when someone that has admin privileges uses the command? It should do it then.

If not, does the docker start/stop command work for you?

[Assaro]

Nvm, i misread what you did. The allowedContainers variable is deprecated. Don't use that anymore. There are commands you can use to grant access to a user or a role on your discord. they are /role and /user

[GBHU753]

@Assaro What is the method for allowing a user to only have vision of a certain container? Do I need to use some role binding?

[GBHU753]

Actually I worked it out by looking at #31. Maybe I missed this but could we make this clear somewhere in the readme. This project is really cool but it would be a shame if someone got turned away from it because they can't work it out.