I assume you want to use your alias without any trailing "arguments" (i.e. in a shell you want to call sole sshConfigHost, not something like sshConfigHost -c "shell code here").
If so, you can put everything in your ~/.ssh/config:
Host friendlyName
RequestTTY yes
Hostname hostname
RemoteCommand docker exec -it containerName bash
(In case there is Host * or so, keep in mind that for each parameter, the first obtained value will be used.)
Now you just do:
ssh friendlyName
and ssh will act as if you did:
ssh -t hostname 'docker exec -it containerName bash'
Define as many Host … sections as you wish. Some of them may use the same Hostname and different RemoteCommand, or whatever. The point is you can build a rich config, so in a shell it's enough to ssh oneword and the config will fill in everything for you, depending on oneword.
The config file is deliberately so powerful, it can specify every option. See man 5 ssh_config. I felt intimidated by this concept (why bother with some "obscure" config while I can specify options and such in the command line like with any other tool?) until I discovered it's neat and convenient. It is the Right Way to use ssh. In general if there is anything you would need to repeat again and again when calling ssh, consider putting it in the config file.
And then there is no need for accompanying aliases in the shell. The whole config is in your ~/.ssh/config.