Cannot connect to emulator in azure storage explorer when only running table service

### Which service(blob, file, queue, table) does this issue concern?
Table
### Which version of the Azurite was used?
Latest
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm, running with docker
### What's the Node.js version?

### What problem was encountered?
When I run `docker run -p 10002:10002 mcr.microsoft.com/azure-storage/azurite azurite-table --tableHost 0.0.0.0 --tablePort 10002` in the vs code powershell cli, the output I see looks like this:
```
Azurite Table service is starting on 0.0.0.0:10002
Azurite Table service successfully started on 0.0.0.0:10002
```
Notice it does not say 'Azurite Table service listening on 0.0.0.0:10002'. When I try to view the emulator in Azure Storage Explorer, it says 'You are attempting to access an emulator storage account without a running emulator. Storage Explorer does not ship with an emulator, you must install your own. It is recommended that you use Azurite. Once you have installed an emulator you can start it and refresh this node.'

### Steps to reproduce the issue?
Do what I did.
If possible, please provide the debug log using the -d parameter, replacing \ with an appropriate path for your OS, or review the instructions for docker containers:

```
-d ""
```

Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.

### Have you found a mitigation/solution?
Nope. I just run all the services together, but I really only need the table service.