The application layer protocol and shouldn’t be a concern for docker. As for the http version, when I execute the command that you provided with more logs, this is what I get:
curl -vvv --http2 -s http://10.100.200.10:8000
* Rebuilt URL to: http://10.100.200.10:8000/
* Trying 10.100.200.10...
* TCP_NODELAY set
* Connected to 10.100.200.10 (10.100.200.10) port 8000 (#0)
> GET / HTTP/1.1
> Host: 10.100.200.10:8000
> User-Agent: curl/7.58.0
> Accept: */*
> Connection: Upgrade, HTTP2-Settings
> Upgrade: h2c
> HTTP2-Settings: AAMAAABkAARAAAAAAAIAAAAA
>
< HTTP/1.1 101 Switching Protocols
< Connection: Upgrade
< Upgrade: h2c
* Received 101
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404
< content-type: text/plain
< content-length: 18
< date: Wed, 02 Feb 2022 14:11:08 GMT
<
* Connection #0 to host 10.100.200.10 left intact
404 page not found
The upgrade to http2 is successful. I don’t get a protocol error on the ausf side (10.100.200.10).
In your case, does this curl request trigger a protocol error on the ausf ?