Closed krasi-georgiev closed 6 years ago
docker run -v /tmp/data:/cncf/data -e NAME=cross-cloud -e CLOUD=packet -e COMMAND=deploy -e BACKEND=file -e PACKET_AUTH_TOKEN=***** -e TF_VAR_packet_project_id=***** -ti registry.cncf.ci/cncf/cross-cloud/provisioning:production
creates the machines and deploys k8s , but fails at the dns resolution.
Unable to connect to the server: dial tcp: lookup ecross-cloud.packet.local on 192.168.1.1:53: no such host
@taylor pointed me to the discovery_nameserver variable,but I couldn't figure it out how to use it and set the correct IP there.
the default is set to https://github.com/crosscloudci/cross-cloud/blob/e4229e79ea141df0c92b24401cd867afe2c863bf/packet/input.tf#L6 how did you come up with this IP?
I would really appreciate if someone can add the missing piece to the puzzle.
cc @taylor , @denverwilliams
creates the machines and deploys k8s , but fails at the dns resolution.
@taylor pointed me to the discovery_nameserver variable,but I couldn't figure it out how to use it and set the correct IP there.
the default is set to https://github.com/crosscloudci/cross-cloud/blob/e4229e79ea141df0c92b24401cd867afe2c863bf/packet/input.tf#L6 how did you come up with this IP?
I would really appreciate if someone can add the missing piece to the puzzle.
cc @taylor , @denverwilliams