Closed lets-data closed 5 months ago
@lets-data , Thanks for your feedback! We will investigate and update as appropriate.
@lets-data Thank you for bringing this to our attention. I've delegated this to content author @tomvcassidy, who will review it and offer their insightful opinions.
Hi @lets-data ! I checked with the product team, and they don't believe that enabling IPv6 is a requirement. Looking back through the commit history for the doc, it seems it was once a requirement and the instructions weren't removed when that changed.
If you wanted to use IPv6, I suspect there would need to be additional JSON parameters added like shown on the Docker documentation here: https://docs.docker.com/config/daemon/ipv6/#use-ipv6-for-the-default-bridge-network
However, even with all of this said, I regret to inform you that the dev team hasn't published an up-to-date Linux container image for a while (https://hub.docker.com/_/microsoft-service-fabric-onebox), and I've been told they don't plan to for the foreseeable future. In light of that, I've been advised to retire this article. I'll be doing that shortly.
Thanks for bringing this issue to our attention. If you find anything else, please let us know.
The following instructions for setting up docker desktop on MacOSX were incorrect for me as I was attempting to install Azure Service Fabric dev env on my desktop. The issues were in the enabling docker desktop for ipv6 scenarios.
Here are the issues:
I seem to have the latest docker desktop. Also, it would be beneficial to know why are we adding this to the configuration (why service fabric would need ipv6 or the specific cidr range)
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.