That advice on the wiki seems to be focused on users who don’t know anything about docker and running with some defaults that might not be ideal.
You can run Sonarr just fine in Portainer. It’s just a wrapper around plain old docker anyway. And if you want to use docker compose, you can still do that in Portainer. I think they call them Stacks in Portainer.
Portainer is just a GUI front end for Docker. If you like it, stick with it. I used it until I moved to Unraid and had zero issues.
OK awesome, thank you for reassuring. I did setup docker first and added portainer with docker, so it sounds like I'm on the right track. Now I can move on to the arrs and will watch a few guides on that.
The warning is about using portainer to initially setup the container, not using it to manage it once setup
If you use docker compose, or even straight docker commands, to initialise the container, it's then fine to use portainer to monitor the status and restart it and things like that.
As a side note, look into dockge instead of portainer. It's foss, and it saves the yaml files in the path of the container, so you can manipulate them manually if you want.
In portainer if for some reason it gets corrupted you lose all the docker-compose.yml