adamsteinbok

To help anyone who's having this issue with an 'insecure' registry: adding the `--insecure` flag to my create command resolved this for me.

A quick look at the [source](https://github.com/docker/cli/blob/968ce1ae4d45722c6ae70aa1dff6ee28d88e976a/cli/registry/client/fetcher.go#L237) indicates that the error messages that are actually helpful in this case are hidden behind debug logging.

As far as I can tell, you need both the 'insecure-registries' entry in the daemon.json AND the `--insecure` flag on the client command.

``` 2023-11-20 15:29:56.423468798 goroutine 85 [syscall, 667 minutes]: 2023-11-20 15:29:56.423536499 syscall.Syscall6(0x0?, 0x0?, 0x0?, 0x0?, 0x0?, 0x0?, 0x0?) 2023-11-20 15:29:56.423607964 syscall/syscall_linux.go:91 +0x30 2023-11-20 15:29:56.423614191 os.(*Process).blockUntilWaitable(0xc00003e6c0) 2023-11-20 15:29:56.423650978 os/wait_waitid.go:32 +0x76 2023-11-20 15:29:56.423656889...

I can't say for sure, but this could be an issue with the [senders replacement handling](https://github.com/AlexxIT/go2rtc/blob/a87dafbbecdc64e4dae78fbbf99688f14301c583/pkg/core/track.go#L79)? To me, it looks like the "target" receiver using a separate mutex to the...

V1.8.2