Artem Kolin

I've got the same error. Do you have any suggestion?

We have almost the same use case. We receive some data from the network and send items to a channel while the background worker processes them. When we have too...

It's fixed in #14

The project looks a bit outdated I wasn't be able to build it. It would be really good if maintainers could accept PR #14 and build new version. Meanwhile I...

@travisghansen Check it out [artemkaxboy/docker-hub-exporter](https://github.com/artemkaxboy/docker-hub-exporter) Please, make sure you do not pass multiple values in one command option if you use command options for namespaces/images. DON'T ``` --namespace="artemkaxboy,nginx" --image="infinityworks/docker-hub-exporter,infinityworks/build-tools" ```...

> Still possible to do multiple namespaces using env var? Yes, for envs you use plural noun and a comma to divide: ```shell --env IMAGES="infinityworks/docker-hub-exporter,infinityworks/build-tools" --env NAMESPACES="artemkaxboy,nginx" ```

I've finally prepared a fully compatible docker image which can be used for super easy migration. Feel free to use it: [artemkaxboy/docker-hub-exporter:legacy](https://github.com/artemkaxboy/docker-hub-exporter/tree/legacy)

> Looks like everything is working perfectly without any changes using your `legacy` tag. Thanks! Thanks for testing!

Hello! Is there any workaround to customize Steve ports at the moment?

Hello, thanks for your report! You are right, default user to shell in to container is always root. I'll consider passing standard user option to connect command, it should be...