{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":716209508,"defaultBranch":"master","name":"moby","ownerLogin":"robmry","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-11-08T16:56:35.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/148866618?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1717618278.0","currentOid":""},"activityList":{"items":[{"before":"8c2e4ca6d63f7d2e8564bee79965c426755748f2","after":"01eecb6cdf9496057af7e3a80503e9b5b46a8eaa","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-11T21:34:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Validate port bindings for gateway_mode=routed\n\nWhen bridge driver opt com.docker.network.bridge.gatway_mode_ipv[46]\nis set to \"routed\", there is no NAT.\n\nWhen there's no NAT, there's no meaning to the HostPort field in a\nport mapping (all the port mapping does is open the container's port),\nand the HostIP field is only used to determine the address family.\n\nSo, check port bindings, and raise errors if fields are unexpectedly\nset when the mapping only applies to a gateway_mode=routed network.\nZero-addresses are allowed, to say the mapping/open-port should be\nIPv4-only or IPv6-only, and host ports are not allowed.\n\nA mapping with no host address, so it applies to IPv4 and IPv6 when\nthe default binding is 0.0.0.0, may include a host port if either\nuses NAT. The port number is ignored for the directly-routed family.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Validate port bindings for gateway_mode=routed"}},{"before":"8f7b9c4d64b5d38694d2727c0107698e7fa303f6","after":"8c2e4ca6d63f7d2e8564bee79965c426755748f2","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-11T16:55:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Validate port bindings for gateway_mode=routed\n\nWhen bridge driver opt com.docker.network.bridge.gatway_mode_ipv[46]\nis set to \"routed\", there is no NAT.\n\nWhen there's no NAT, there's no meaning to the HostPort field in a\nport mapping (all the port mapping does is open the container's port),\nand the HostIP field is only used to determine the address family.\n\nSo, check port bindings, and raise errors if fields are unexpectedly\nset when the mapping only applies to a gateway_mode=routed network.\nZero-addresses are allowed, to say the mapping/open-port should be\nIPv4-only or IPv6-only, and host ports are not allowed.\n\nA mapping with no host address, so it applies to IPv4 and IPv6 when\nthe default binding is 0.0.0.0, may include a host port if either\nuses NAT. The port number is ignored for the directly-routed family.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Validate port bindings for gateway_mode=routed"}},{"before":"f3f20c3a862ff90c7e7b0ee07dabe2176ed0a170","after":"87794b3030c83d0f42fd530d9f41080a6506494d","ref":"refs/heads/master","pushedAt":"2024-06-11T16:48:25.000Z","pushType":"push","commitsCount":100,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Merge pull request #47946 from thaJeztah/remove_platforms_platform_alias\n\nremove uses of platforms.Platform alias","shortMessageHtmlLink":"Merge pull request moby#47946 from thaJeztah/remove_platforms_platfor…"}},{"before":"66639691e18c4e8558463eec1574b13af6cfe16f","after":"8f7b9c4d64b5d38694d2727c0107698e7fa303f6","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-11T16:01:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Validate port bindings for gateway_mode=routed\n\nWhen bridge driver opt com.docker.network.bridge.gatway_mode_ipv[46]\nis set to \"routed\", there is no NAT.\n\nWhen there's no NAT, there's no meaning to the HostPort field in a\nport mapping (all the port mapping does is open the container's port),\nand the HostIP field is only used to determine the address family.\n\nSo, check port bindings, and raise errors if fields are unexpectedly\nset when the mapping only applies to a gateway_mode=routed network.\nZero-addresses are allowed, to say the mapping/open-port should be\nIPv4-only or IPv6-only, and host ports are not allowed.\n\nA mapping with no host address, so it applies to IPv4 and IPv6 when\nthe default binding is 0.0.0.0, may include a host port if either\nuses NAT. The port number is ignored for the directly-routed family.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Validate port bindings for gateway_mode=routed"}},{"before":"059bca4136d3b36847c937a3b346e770a08b51d2","after":"66639691e18c4e8558463eec1574b13af6cfe16f","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-11T15:28:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Validate port bindings for gateway_mode=routed\n\nWhen bridge driver opt com.docker.network.bridge.gatway_mode_ipv[46]\nis set to \"routed\", there is no NAT.\n\nWhen there's no NAT, there's no meaning to the HostPort field in a\nport mapping (all the port mapping does is open the container's port),\nand the HostIP field is only used to determine the address family.\n\nSo, check port bindings, and raise errors if fields are unexpectedly\nset when the mapping only applies to a gateway_mode=routed network.\nZero-addresses are allowed, to say the mapping/open-port should be\nIPv4-only or IPv6-only, and host ports are not allowed.\n\nA mapping with no host address, so it applies to IPv4 and IPv6 when\nthe default binding is 0.0.0.0, may include a host port if either\nuses NAT. The port number is ignored for the directly-routed family.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Validate port bindings for gateway_mode=routed"}},{"before":"7491fe93dada333344cad28a1fb797628cb71ffe","after":"837b3f9576c5a3cdcae378905d411bade54c9d26","ref":"refs/heads/allow_startup_with_no_ip6tables","pushedAt":"2024-06-07T16:43:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Allow startup with no kernel support for ip6_tables\n\nBefore \"ip6tables\" was enabled by default, dockerd would start normally\nwhen:\n- the kernel had no IPv6 support, or\n- docker is running as docker-in-docker, and the host doesn't have kernel\n module 'ip6_tables' loaded.\n\nNow, the bridge driver will try to set up its ip6tables chains and it'll\nfail. By not treating that as an error, the daemon will start and IPv4\nwill work normally.\n\nA subsequent attempt to create an IPv6 network will fail with an error\nabout ip6tables. At that point, the user's options are:\n- set \"ip6tables\":false in daemon config\n- in the DinD case, \"modprobe ip6_tables\" on the host, or start dockerd\n on the host with ip6tables enabled (causing the kernel module load).\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Allow startup with no kernel support for ip6_tables"}},{"before":"c54fd49cedf8eed0248a1c440d0dff16cab2d189","after":"059bca4136d3b36847c937a3b346e770a08b51d2","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-06T16:06:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Remove unused bridge.driver.portAllocator\n\nIt was added so that tests could replace it before it was picked\nup and used by a new network's PortMapper, so that tests were isolated\nfrom each other. Now the PortMapper is not used by the bridge driver,\nneither is driver's portAllocator.\n\nInstead of replacing the driver.portAllocator in tests, reset the\nsingleton instance using its ReleaseAll().\n\nUn-export portallocator.NewInstance, now the tests aren't using it.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Remove unused bridge.driver.portAllocator"}},{"before":"05ae0f04bfc397f3a63554d60ef125abd471f7da","after":"c54fd49cedf8eed0248a1c440d0dff16cab2d189","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-06T13:34:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"2ebf19129fe56f56800cfbdf87e59883b90671dc","after":"f3f20c3a862ff90c7e7b0ee07dabe2176ed0a170","ref":"refs/heads/master","pushedAt":"2024-06-06T09:39:24.000Z","pushType":"push","commitsCount":35,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Merge pull request #47602 from robmry/internal_resolver_for_default_bridge\n\nAdd resolver for default bridge, remove default nameservers","shortMessageHtmlLink":"Merge pull request moby#47602 from robmry/internal_resolver_for_defau…"}},{"before":"4c0e8734b88344eb879a9146bd5128b1851a11d8","after":"05ae0f04bfc397f3a63554d60ef125abd471f7da","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-05T23:31:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"8ce32a2ef17e2953f0726dbb20a080cc9dbda83b","after":"4c0e8734b88344eb879a9146bd5128b1851a11d8","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-05T22:25:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"f6cbc1591487f06f8bf53624b1761cfcd8625a6d","after":"8ce32a2ef17e2953f0726dbb20a080cc9dbda83b","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-05T21:19:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"2421d55e2a1535d24f9aa0ce3e96b0f4dc23c1a0","after":"7491fe93dada333344cad28a1fb797628cb71ffe","ref":"refs/heads/allow_startup_with_no_ip6tables","pushedAt":"2024-06-05T20:39:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Allow startup with no kernel support for ip6_tables\n\nBefore \"ip6tables\" was enabled by default, dockerd would start normally\nwhen:\n- the kernel had no IPv6 support, or\n- docker is running as docker-in-docker, and the host doesn't have kernel\n module 'ip6_tables' loaded.\n\nNow, the bridge driver will try to set up its ip6tables chains and it'll\nfail. By not treating that as an error, the daemon will start and IPv4\nwill work normally.\n\nA subsequent attempt to create an IPv6 network will fail with an error\nabout ip6tables. At that point, the user's options are:\n- set \"ip6tables\":false in daemon config\n- in the DinD case, \"modprobe ip6_tables\" on the host, or start dockerd\n on the host with ip6tables enabled (causing the kernel module load).\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Allow startup with no kernel support for ip6_tables"}},{"before":"0e09a7c157e130fa02f191845b66115d11095fe2","after":"2421d55e2a1535d24f9aa0ce3e96b0f4dc23c1a0","ref":"refs/heads/allow_startup_with_no_ip6tables","pushedAt":"2024-06-05T20:19:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Allow startup with no kernel support for ip6_tables\n\nBefore \"ip6tables\" was enabled by default, dockerd would start normally\nwhen:\n- the kernel had no IPv6 support, or\n- docker is running as docker-in-docker, and the host doesn't have kernel\n module 'ip6_tables' loaded.\n\nNow, the bridge driver will try to set up its ip6tables chains and it'll\nfail. By not treating that as an error, the daemon will start and IPv4\nwill work normally.\n\nA subsequent attempt to create an IPv6 network will fail with an error\nabout ip6tables. At that point, the user's options are:\n- set \"ip6tables\":false in daemon config\n- \"modprobe ip6_tables\" on the host in the DinD case\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Allow startup with no kernel support for ip6_tables"}},{"before":null,"after":"0e09a7c157e130fa02f191845b66115d11095fe2","ref":"refs/heads/allow_startup_with_no_ip6tables","pushedAt":"2024-06-05T20:11:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Allow startup with no kernel support for ip6_tables\n\nBefore \"ip6tables\" was enabled by default, dockerd would start normally\nwhen:\n- the kernel had no IPv6 support, or\n- docker is running as docker-in-docker, and the host doesn't have kernel\n module 'ip6_tables' loaded.\n\nNow, the bridge driver will try to set up its ip6tables chains and it'll\nfail. By not treating that as an error, the daemon will start and IPv4\nwill work normally.\n\nAn attempt to create an IPv6 network will fail with an error about\nip6tables. At that point, the user's options are:\n- set \"ip6tables\":false in daemon config\n- \"modprobe ip6_tables on the host in the DinD case\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Allow startup with no kernel support for ip6_tables"}},{"before":"630930b9f8ea7935cd52a60e74150814cb634a99","after":"d365702dbd389f3a61ad0862d0c2889022105f42","ref":"refs/heads/internal_resolver_for_default_bridge","pushedAt":"2024-06-05T19:27:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"No default nameservers for internal resolver\n\nDon't fall-back to Google's DNS servers in a network that has an\ninternal resolver.\n\nNow the default bridge uses the internal resolver, the only reason a\nnetwork started by the daemon should end up without any upstream\nservers is if the host's resolv.conf doesn't list any. In this case,\nthe '--dns' option can be used to explicitly configure nameservers\nfor a container if necessary.\n\n(Note that buildkit's containers do not have an internal resolver, so\nthey will still set up Google's nameservers if the host has no\nresolvers that can be used in the container's namespace.)\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"No default nameservers for internal resolver"}},{"before":"c586d6a23940a23d54888c7430fe287ef7686e55","after":"1a8b58282d834d2e6cde1c86b434613dafbe7dd4","ref":"refs/heads/fix_netiputil_toprefix","pushedAt":"2024-06-05T16:29:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Handle IPv4-mapped IPv6 addrs in netiputil.ToPrefix\n\nnetiputil.ToPrefix called Unmap() on the address, but didn't adjust\n'ones' for an IPv4-mapped IPV6 address. So, it was off by 96 and\nnetip.PrefixFrom failed.\n\nSo, preserve the IPv4-mapping in that case.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Handle IPv4-mapped IPv6 addrs in netiputil.ToPrefix"}},{"before":"a717a1cd5ab8fcdcbae74ce9f7db3efb6a1afcc1","after":"c586d6a23940a23d54888c7430fe287ef7686e55","ref":"refs/heads/fix_netiputil_toprefix","pushedAt":"2024-06-05T16:28:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Handle IPv4-mapped IPv6 addrs in netip.ToPrefix\n\nnetiputil.ToPrefix called Unmap() on the address, but didn't adjust\n'ones' for an IPv4-mapped IPV6 address. So, it was off by 96 and\nnetip.PrefixFrom failed.\n\nSo, preserve the IPv4-mapping in that case.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Handle IPv4-mapped IPv6 addrs in netip.ToPrefix"}},{"before":null,"after":"a717a1cd5ab8fcdcbae74ce9f7db3efb6a1afcc1","ref":"refs/heads/fix_netiputil_toprefix","pushedAt":"2024-06-05T16:23:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Handle IPv4-mapped IPv6 addrs in netip.ToPrefix\n\nnetip.ToPrefix called Unmap() on the address, but didn't adjust\n'ones' for an IPv4-mapped IPV6 address. So, it was off by 96 and\nnetip.PrefixFrom failed.\n\nSo, preserve the IPv4-mapping in that case.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Handle IPv4-mapped IPv6 addrs in netip.ToPrefix"}},{"before":"d44269ea1417a2c90fc39c2efee9fd665928cfae","after":"630930b9f8ea7935cd52a60e74150814cb634a99","ref":"refs/heads/internal_resolver_for_default_bridge","pushedAt":"2024-06-05T16:02:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"No default nameservers for internal resolver\n\nDon't fall-back to Google's DNS servers in a network that has an\ninternal resolver.\n\nNow the default bridge uses the internal resolver, the only reason a\nnetwork started by the daemon should end up without any upstream\nservers is if the host's resolv.conf doesn't list any. In this case,\nthe '--dns' option can be used to explicitly configure nameservers\nfor a container if necessary.\n\n(Note that buildkit's containers do not have an internal resolver, so\nthey will still set up Google's nameservers if the host has no\nresolvers that can be used in the container's namespace.)\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"No default nameservers for internal resolver"}},{"before":"bc962e6800435e7e485d602922573708f3cfb9e2","after":"f6cbc1591487f06f8bf53624b1761cfcd8625a6d","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-05T15:21:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"026c263c0ccf01f9e5dbf75581e26110d7da005c","after":"bc962e6800435e7e485d602922573708f3cfb9e2","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-05T14:45:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"6f00ac760675b7d61f400b7ec081def57c786e90","after":"d44269ea1417a2c90fc39c2efee9fd665928cfae","ref":"refs/heads/internal_resolver_for_default_bridge","pushedAt":"2024-06-05T11:03:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"No default nameservers for internal resolver\n\nDon't fall-back to Google's DNS servers in a network that has an\ninternal resolver.\n\nNow the default bridge uses the internal resolver, the only reason a\nnetwork started by the daemon should end up without any upstream\nservers is if the host's resolv.conf doesn't list any. In this case,\nthe '--dns' option can be used to explicitly configure nameservers\nfor a container if necessary.\n\n(Note that buildkit's containers do not have an internal resolver, so\nthey will still set up Google's nameservers if the host has no\nresolvers that can be used in the container's namespace.)\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"No default nameservers for internal resolver"}},{"before":"38b34a7ce8fe72a74a0d5676b206569a2cb4bff5","after":"6f00ac760675b7d61f400b7ec081def57c786e90","ref":"refs/heads/internal_resolver_for_default_bridge","pushedAt":"2024-06-05T08:42:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"No default nameservers for internal resolver\n\nDon't fall-back to Google's DNS servers in a network that has an\ninternal resolver.\n\nNow the default bridge uses the internal resolver, the only reason a\nnetwork started by the daemon should end up without any upstream\nservers is if the host's resolv.conf doesn't list any. In this case,\nthe '--dns' option can be used to explicitly configure nameservers\nfor a container if necessary.\n\n(Note that buildkit's containers do not have an internal resolver, so\nthey will still set up Google's nameservers if the host has no\nresolvers that can be used in the container's namespace.)\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"No default nameservers for internal resolver"}},{"before":"e61b9db3f8cab82827f33bfe14cfc2fb818e4d3f","after":"026c263c0ccf01f9e5dbf75581e26110d7da005c","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-04T15:55:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"e066f01256e80b3ab07d5692648ba711033c4ca9","after":"e61b9db3f8cab82827f33bfe14cfc2fb818e4d3f","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-06-04T13:57:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"d594859bed6ffd536b629cb4ed9bf6b84b089ad8","after":"e066f01256e80b3ab07d5692648ba711033c4ca9","ref":"refs/heads/portmapper_fixes_and_nonat","pushedAt":"2024-05-30T18:05:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"},"commit":{"message":"Bind the same port for multiple addresses\n\nWithout this change, if a port mapping did not specify a host address\nand the network was IPv6-enabled, the same port would be allocated for\nmappings from '0.0.0.0' and '::'. But, if the port mapping was specified\nwith explicit addresses even, for example:\n -p 0.0.0.0:8080-8083:80 -p '[::]:8083-8080:80'\n\nThis change looks for port mappings that only differ in the host IP\naddress, and makes sure it allocates the same port for all of them. If\nit can't, it fails with an error.\n\nSigned-off-by: Rob Murray ","shortMessageHtmlLink":"Bind the same port for multiple addresses"}},{"before":"33f9a5329a9259bc361f925a09633674878650be","after":null,"ref":"refs/heads/windns_proxy_default","pushedAt":"2024-05-29T17:53:43.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"}},{"before":"41ddc47bbfacae438793238126be4d268ddf7469","after":null,"ref":"refs/heads/non-experimental-ip6tables","pushedAt":"2024-05-29T17:51:56.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"}},{"before":"87506142d88fa3c0e10963144bef0651b60cfafc","after":null,"ref":"refs/heads/47716_no_dns_req_to_self","pushedAt":"2024-05-29T17:48:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"robmry","name":"Rob Murray","path":"/robmry","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/148866618?s=80&v=4"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEYq2qnwA","startCursor":null,"endCursor":null}},"title":"Activity · robmry/moby"}