Closed horseinthesky closed 3 years ago
iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 127.0.0.1 --dport 49282 -j DNAT --to-destination 192.168.49.2:8443 ! -i br-c463e713e81d: : iptables v1.8.7 (legacy): unknown option "--dport"
Hmm, that is supposed to be a standard tcp option, see iptables-extensions(8)
tcp
These extensions can be used if `--protocol tcp' is specified. It provides the following options:
[!] --source-port,--sport port[:port]
Source port or port range specification. This can either be a service name or a port number. An inclusive range can also be specified, using the format first:last. If the first port
is omitted, "0" is assumed; if the last is omitted, "65535" is assumed. The flag --sport is a convenient alias for this option.
[!] --destination-port,--dport port[:port]
Destination port or port range specification. The flag --dport is a convenient alias for this option.
Do running other docker containers work OK ?
@afbjorklund I'm sorry for bothering. That was an Arch issue: it's updated a kernel and unmounted old kernel modules. Reboot fixed it.
Just faced the same issue, rebooting solved it. Way too often, I update then try to do work that requires unmounted kernel modules hahaha.
Steps to reproduce the issue:
Unable to create cluster.
Arch minikube 1.17.1 from pacman
Clean start attempt
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command: `` minikube logs ๐คท Profile "minikube" not found. Run "minikube profile list" to view all profiles. ๐ To start a cluster, run: "minikube start"