CryptoGeek

Did you try naming the registry anything else than `PUBLIC`? I'm using it like this and it's working perfectly fine: ``` environment: WUD_REGISTRY_HUB_dockerhub_LOGIN: ${DOCKER_HUB_LOGIN} WUD_REGISTRY_HUB_dockerhub_PASSWORD: ${DOCKER_HUB_TOKEN} ```

Valve please, you are selling me a dock but don't support changing the layout of a connected keyboard? This issue is open for so long now and a really basic...

As a workaroud you can set a healthcheck, just like I already tried. Instead of using localhost use the name of your container, like this: ``` healthcheck: test: curl --fail...

Are your images in docker-compose.yml also prefixed with that registry? I don't know if WUD has a way to find out about the default registry. As far as I can...

You are providing a timezone via environment variable and by mounting your servers timezone into the container. Any chance those two are different? Maybe that could cause weird behavior? I'd...

Partially a possible duplicate of #620 . I think this is mixing two different phenomenons (socket hang up and read properties of undefined (reading tag)

+1 for sharing persons and face detection info via partner sharing. I mean a person is always the same, no matter who uploaded the photo. It just feels weird that...

> > Wouldn't it be easier to treat face detection and identification globally and not per user? > > No, this would have bad privacy implications on instances with users...

those error messages, especially the authorized part, read to me like your remote docker daemon requires authentication. Are you sure, you set that up correctly without encryption on your remotes?...