【2023-07-27】k8s修改了网络范围，重新部署pod报错failed to delegate add: failed to set bridge addr: “cni0“ already ha

最新推荐文章于 2024-08-28 11:42:40 发布
最新推荐文章于 2024-08-28 11:42:40 发布
阅读量262 收藏
点赞数
分类专栏： k8s 文章标签： kubernetes 网络 容器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u013012406/article/details/131956587
版权
在K8s中修改网络范围后，尝试重新部署Pod时遇到错误，Pod状态为ContainerCreating。错误信息显示CNI插件在设置Pod网络时因IP冲突无法创建桥接地址。解决方法是删除错误配置的网卡cni0并让系统自动重建，成功更新网卡IP后，Pod可以正常运行。
摘要由CSDN通过智能技术生成

k8s修改了网络范围，重新部署pod报错：

[root@master ~]$kubectl  get pods -A -o wide
NAMESPACE      NAME                             READY   STATUS              RESTARTS   AGE     IP             NODE     NOMINATED NODE   READINESS GATES
default        test-k8s-68bb74d654-5mvwd        1/1     Running             0          2d19h   10.244.0.6     node1    <none>           <none>
default        test-k8s-68bb74d654-b4ntt        1/1     Running             0          2d19h   10.244.0.6     node3    <none>           <none>
default        test-k8s-68bb74d654-cfgh7        1/1     Running             0          2d19h   10.244.0.7     node3    <none>           <none>
default        test-k8s-68bb74d654-lzdv7        1/1     Running             0          2d19h   10.244.0.5     node1    <none>           <none>
default        test-k8s-68bb74d654-sc5js        1/1     Running             0          2d19h   10.244.0.7     node2    <none>           <none>
default        test-pod                         0/1     ContainerCreating   0          4m5s    <none>         node2    <none>           <none>
default        testapp                          0/1     ContainerCreating   0          81s     <none>         node1    <none>           <none>
kube-flannel   kube-flannel-ds-gcm48            1/1     Running             0          15m     10.10.26.118   node3    <none>           <none>
kube-flannel   kube-flannel-ds-lfh57            1/1     Running             0          15m     10.10.26.116   node1    <none>           <none>
kube-flannel   kube-flannel-ds-q68vj            1/1     Running             0          15m     10.10.26.117   node2    <none>           <none>
kube-flannel   kube-flannel-ds-vxpd4            1/1     Running             0          15m     10.10.26.115   master   <none>           <none>
kube-system    coredns-7f6cbbb7b8-5smwq         1/1     Running             0          8d      10.244.0.2     master   <none>           <none>
kube-system    coredns-7f6cbbb7b8-fnqq8         1/1     Running             0          8d      10.244.0.3     master   <none>           <none>
kube-system    etcd-master                      1/1     Running             0          8d      10.10.26.115   master   <none>           <none>
kube-system    kube-apiserver-master            1/1     Running             0          8d      10.10.26.115   master   <none>           <none>
kube-system    kube-controller-manager-master   1/1     Running             0          8d      10.10.26.115   master   <none>           <none>
kube-system    kube-proxy-8f955                 1/1     Running             0          8d      10.10.26.115   master   <none>           <none>
kube-system    kube-proxy-knvqv                 1/1     Running             0          8d      10.10.26.118   node3    <none>           <none>
kube-system    kube-proxy-tx75f                 1/1     Running             0          8d      10.10.26.116   node1    <none>           <none>
kube-system    kube-proxy-wjdvl                 1/1     Running             0          8d      10.10.26.117   node2    <none>           <none>
kube-system    kube-scheduler-master            1/1     Running             0          8d      10.10.26.115   master   <none>           <none>

查看pod日志，发现有报错：

[root@master ~]$kubectl describe pod testapp
Name:         testapp
Namespace:    default
Priority:     0
Node:         node1/10.10.26.116
Start Time:   Thu, 27 Jul 2023 11:12:24 +0800
Labels:       run=testapp
Annotations:  <none>
Status:       Pending
IP:
IPs:          <none>
Containers:
  testapp:
    Container ID:
    Image:          ccr.ccs.tencentyun.com/k8s-tutorial/test-k8s:v1
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-qvfw7 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-qvfw7:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age                  From               Message
  ----     ------                  ----                 ----               -------
  Normal   Scheduled               110s                 default-scheduler  Successfully assigned default/testapp to node1
  Warning  FailedCreatePodSandBox  109s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "1ff628b02425798ccc88f2880db61848e64605480ca9ea3ccb97a19193b71ac5" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  108s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "09e6e121e1acba0422a63d9de1930583fd807a435ae9a19da1e50eacc4af34a7" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  107s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "90defd5fae80935e7a0b25f0354faf7607b47fced7e3a2e235d2f06098214897" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  106s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "3a3a816d57bb7f0e95f8d2f8b6abc3de743cc93e56459b0462fd072b79dc0951" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  104s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "a67dede7c0d84ba12b1becc8a2964da879666dbc119f407799cc0050c59301e9" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  103s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "807d42dcc6c6cc7a7c14b69ac5b2e966a57d413afe86fbdd28dd97be6a90160e" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  102s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "53804a5085258232c1395f89d2ba877c6a810a4db14bcb681c1b8dedbd7bd8d8" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  101s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "ec8c2ae4b1f2679c202fa40967c789b8371b4cd945f7179bd33a1b90eb3ee875" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Warning  FailedCreatePodSandBox  100s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "336db115dbc1be122101a5d21882c2005b3d887f55051dd37852360171d19757" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24
  Normal   SandboxChanged          97s (x12 over 108s)  kubelet            Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  96s (x4 over 99s)    kubelet            (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "0a50914bccdd5f177115f1309f2f2bd1767d9dcb23f210c8fede297c15e7dbb1" network for pod "testapp": networkPlugin cni failed to set up pod "testapp_default" network: failed to delegate add: failed to set bridge addr: "cni0" already has an IP address different from 10.100.0.1/24

查看网卡ip，发现还是旧的ip：cni0 10.244.0.1

[root@node1 ~]$ifconfig
cni0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet 10.244.0.1  netmask 255.255.255.0  broadcast 10.244.0.255
        inet6 fe80::f880:cff:fed5:dda5  prefixlen 64  scopeid 0x20<link>
        ether fa:80:0c:d5:dd:a5  txqueuelen 1000  (Ethernet)
        RX packets 498  bytes 14104 (13.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 425  bytes 26730 (26.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:e7:db:fd:9e  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

解决方法：将这个错误的网卡删除掉，系统会自动重建。


[root@node1 ~]$ifconfig cni0 down
[root@node1 ~]$ip link delete cni0
[root@node1 ~]$
[root@node1 ~]$ifconfig
cni0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet 10.100.0.1  netmask 255.255.255.0  broadcast 10.100.0.255
        inet6 fe80::849c:66ff:fef0:50ce  prefixlen 64  scopeid 0x20<link>
        ether 86:9c:66:f0:50:ce  txqueuelen 1000  (Ethernet)
        RX packets 1  bytes 28 (28.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 446 (446.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:e7:db:fd:9e  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

再次检查就正常了：

[root@master ~]$kubectl  get pods -A -o wide
NAMESPACE      NAME                             READY   STATUS    RESTARTS      AGE     IP             NODE     NOMINATED NODE   READINESS GATES
default        test-k8s-68bb74d654-5mvwd        1/1     Running   0             2d19h   10.244.0.6     node1    <none>           <none>
default        test-k8s-68bb74d654-b4ntt        1/1     Running   0             2d19h   10.244.0.6     node3    <none>           <none>
default        test-k8s-68bb74d654-cfgh7        1/1     Running   0             2d19h   10.244.0.7     node3    <none>           <none>
default        test-k8s-68bb74d654-lzdv7        1/1     Running   0             2d19h   10.244.0.5     node1    <none>           <none>
default        test-k8s-68bb74d654-sc5js        1/1     Running   0             2d19h   10.244.0.7     node2    <none>           <none>
default        test-pod                         1/1     Running   0             16m     10.100.0.149   node2    <none>           <none>
default        testapp                          1/1     Running   0             14m     10.100.0.2     node1    <none>           <none>
kube-flannel   kube-flannel-ds-gcm48            1/1     Running   0             28m     10.10.26.118   node3    <none>           <none>
kube-flannel   kube-flannel-ds-lfh57            1/1     Running   0             28m     10.10.26.116   node1    <none>           <none>
kube-flannel   kube-flannel-ds-q68vj            1/1     Running   0             28m     10.10.26.117   node2    <none>           <none>
kube-flannel   kube-flannel-ds-vxpd4            1/1     Running   0             28m     10.10.26.115   master   <none>           <none>
kube-system    coredns-7f6cbbb7b8-5smwq         0/1     Running   3 (28s ago)   8d      10.244.0.2     master   <none>           <none>
kube-system    coredns-7f6cbbb7b8-fnqq8         0/1     Running   3 (52s ago)   8d      10.244.0.3     master   <none>           <none>
kube-system    etcd-master                      1/1     Running   0             8d      10.10.26.115   master   <none>           <none>
kube-system    kube-apiserver-master            1/1     Running   0             8d      10.10.26.115   master   <none>           <none>
kube-system    kube-controller-manager-master   1/1     Running   0             8d      10.10.26.115   master   <none>           <none>
kube-system    kube-proxy-8f955                 1/1     Running   0             8d      10.10.26.115   master   <none>           <none>
kube-system    kube-proxy-knvqv                 1/1     Running   0             8d      10.10.26.118   node3    <none>           <none>
kube-system    kube-proxy-tx75f                 1/1     Running   0             8d      10.10.26.116   node1    <none>           <none>
kube-system    kube-proxy-wjdvl                 1/1     Running   0             8d      10.10.26.117   node2    <none>           <none>
kube-system    kube-scheduler-master            1/1     Running   0             8d      10.10.26.115   master   <none>           <none>

城风漫漫
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
failed to delegate add: failed to set bridge addr: “cni0“ already has an IP address different from 1
weixin_42562106的博客
03-26 6276
当迁移集群之后，拉取镜像报cni网络错误，如下 先停掉网卡 ifconfig eni0 down #删除 ip link delete cni0 #注意删除之后不会重新生成了网卡了，需要重启初始化集群，以前老的版本是自己会重启 删除之后 初始化之前可以修改你需要的网段 /run/flannel/subnet.env [root@node90 ~]# cat /run/flannel/subnet.env FLANNEL_NETWORK=172.16.0.0/16 FLANNEL_SUBNET=172.
K8S网络探究
油纸雨伞的博客
04-26 649
重度参考凤凰架构和Kubernets in Action，目的是了解K8S里面网络如何设计的，以及选用的原则。为了解决容器网络问题:容器和容器容器和宿主机跨物理机的容器通信容器间网络如何通信?主机模式: 使用宿主机的网络，没有隔离。(个人感觉不能和其他的隔离的网络进行通信。容器模式：加入到已有的容器网络overlay模式: calico使用ip on ip进行网络隔离和通信，新能损耗在20%。
k8s部署ingress-nginx，容器状态是一直是ContainerCreating：“cni0“ already has an IP address different from......
qq_52787609的博客
05-04 289
k8s配置ingress的时候，ingress-nginx-controller状态一直是ContainerCreating。
k8s报错：failed to set bridge add :“cni0“ already has IP address different from xxxxxx解决
weixin_64341957的博客
08-02 122
cni的网卡地址与k8s集群内连接地址不一样，查了一下原因是因为操作系统使用的是麒麟的操作系统这是一个bug，解决方法直接 ip link cni0 删掉网卡让他重启就好了。排查思路：首先看system下的pod是否全部启动成功 --> 我的服务依靠nacos中间件，nacos得先启动 --> 排查中间件nacos发现报错。今天遇见一个问题，k8s部署完后里面的pod起不来。于是检测了一下cni0的网卡，果然发现了问题所在。
K8S部署系统异常-FailedCreatePodSandBox：network: failed to set bridge addr: “cni0“ already has an IP addres
一掬净土
01-12 3426
由于系统磁盘不足，导致k8s部分线程死掉，搞定之后，部署项目，报以下异常：FailedCreatePodSandBox network: failed to set bridge addr: “cni0” already has an IP address different from 10.100.1.1/24 意思是说：设置网桥地址失败：“cni0”的IP地址与10.100.1.1/24不同。 Normal SandboxChanged 7m59s (x294 over 12m).
kubernetes failed to set bridge addr: “cni0“ already has an IP address different from
面向未来的历史
03-10 2351
背景： centos 安装kubernetes 后，并初始化mater 执行： kubectl get pod -A dns 状态为 ContainerCreating 看下日志： kubectl logs coredns-6d8c4cb4d-6b5k2 -n kube-system Warning FailedCreatePodSandBox 22m kubelet Failed to create pod sandbox: rp
解决k8s"failed to set bridge addr: "cni0" already has an IP address different from 10.244.1.1/24"
热门推荐
ST_君华的博客
03-07 1万+
测试环境由于机房断电，导致对应虚拟机暴力重启，之后所在k8s服务error，查看系统日志，发现k8s三个节点的flannel文件均丢失。 1.首先我们重新配置k8s的flannel文件，可以参考其他环境的文件配置，也可以重新安装插件生成，会在/run下面生成flannel文件夹，下面包含网络配置环境变量 注明：三个节点的subnet网段不能不同 2.重配flannel之后发现，有两个...
Kubernetes之network: failed to set bridge addr: “cni0“ already has an IP address different from xxx问题
ibless的博客
08-09 9306
Kubernetes之network: failed to set bridge addr: "cni0" already has an IP address different from xxx问题1 问题2 解决方案 1 问题 在使用Kubernetes部署应用时发现有Pod一直不能创建成功，使用kubectl describe pods <pod-name> -n <namespace>得到的结果如下图： 从上面的截图中看到问题出现在给Pod分配IP上，意思是cni0的IP不
k8s paas部署
农夫运维
10-26 3463
服务器 角色 192.168.80.153 mster1、etcd1、docker、 flannel、 harbor 192.168.80.145 mster2、etcd2、docker、flannel 192.168.80.144 mster3、etcd3、docker、 flannel 192.168.80.154 nod1、docker、flannel、nginx...
二进制安装k8s
nsydgs的博客
07-29 1346
Kubernetes概述
Kubernetes：（十八）flannel网络
ver_mouth__的博客
08-15 3600
覆盖网络，在基础网络上叠加的一种虚拟网络技术模式，该网络中的主机通过虚拟链路连接起来类似VPN隧道，原理为在物理网络上实现的逻辑网络将源数据包封装到UDP中，并使用基础网络的IP/MAC作为外层包头进行封装，然后在以太网上传输，到达目的地后由隧道断电解封并将数据发给目标地址是Overlay网络的一种，也是将源数据包封装在另一种网络包中进行路由转发和通信，目前已支持UDP、VXLAN、AWS VPN和GCE路由等数据转发方式特点hostgw这种方式就是直接路由vxlan。...
CNI网络插件之flannel
m0_48594855的博客
07-05 3001
CNI网络插件之flannelCNI网络插件之flannel CNI网络插件之flannel 上篇文章《CNI插件之CNI插件最简实现之macvlan plugin》我们介绍了macvlan插件，通说使用与分析，我们知道: macvlan插件在集群多节点上，要每个节点都放配置文件, 比如/etc/cni/net.d/10-maclannet.conf, 并且各个节点的子网不能冲突。 macvlan插件默认网关的设置上还需要考虑ip是否已经存在，插件并不会自动帮我们设置,需要手动配置。 macvlan插件在
为什么k8s节点要保持配置一致
骑上单车去旅行的博客
08-28 858
如果节点的配置不一致，可能会导致应用程序无法正常运行或出现不可预测的错误。通过保持节点配置一致，可以确保资源利用率的均衡。K8s集群通过调度器将容器调度到可用的节点上，如果节点的配置不一致，某些节点可能会拥有更多的资源，而其他节点可能过载或闲置。通过自动化配置管理工具，可以确保所有节点的配置保持一致，减少了管理的复杂性和工作量。通过保持一致的配置，并及时应用安全补丁和更新，可以降低系统受到攻击的风险。总之，Kubernetes节点保持配置一致是为了确保资源利用率的均衡、系统的稳定性、简化管理和提高安全性。
K8s系列之：K8s OPERATOR是什么
最新发布
zhengzaifeidelushang的博客
08-28 789
Kubernetes 的 Operator 模式概念允许你在不修改 Kubernetes 自身代码的情况下， 通过为一个或多个自定义资源关联控制器来扩展集群的能力。Operator 是 Kubernetes API 的客户端， 充当自定义资源的控制器。部署 Operator 最常见的方法是将自定义资源及其关联的控制器添加到你的集群中。Operator 模式会封装你编写的（Kubernetes 本身提供功能以外的）任务自动化代码。如果生态系统中没有可以实现你目标的 Operator，你可以自己编写代码。
k8s的组件以及安装
Hai990218的博客
08-28 1008
分为主节点和node节点，主节点就是核心，kube-apiserver大脑：所有的一切都要通过kube-apiserver来调用，所有的一切最终都要保存到etcd中，etcd就是保存集群信息的数据库，怎么部署都是靠kube-controller-manager，往哪里部署靠kube-scheduler。到了node节点上，kubelet负责真正部署、控制容器，跨主机网络之间通信通过kube-proxy，服务是由底层docker来启动的。流程图kube-apiserver先接受信息，kube-
K8S集群中驱逐节点
小橙子的笔记屋
08-22 235
K8S集群驱逐节点
kubenetes--资源调度
小李学不完的博客
08-25 1024
资源调度：Label和Selector：标签（Label）、选择器（Selector）。Deployment--无状态应用：功能、配置文件。StatefulSet：功能、配置文件。DaemonSet：配置文件、不指定Node节点、指定Node节点、滚动更新。HPA自动扩/缩容：开启指标服务、cpu、内存指标监控、自定义metrics。
k8s之Pod对象多种调度方式
Linux运维老纪的博客
08-23 1142
在Kubernetes中，Pod对象可以通过多种方式进行调度，包括但不限于：默认调度器：ubernetes自带的默认调度器根据集群中各节点的可用资源、亲和性规则、反亲和性规则等来调度Pod到最合适的节点。 自定义调度器：通过实现Kubernetes的调度器扩展点，可以编写自定义调度逻辑。亲和性/反亲和性规则：通过设置Pod的affinity（亲和性）和anti-affinit（反亲和性）规则，可以指定Pod应该或者不应该被调度到某些节点上。手动指定节点：如果如果有特定需求，可以在创建Pod时手动指定。
Docker使用时候报错Failed to deploy '<unknown> Dockerfile: Dockerfile': Can't retrieve image ID from build stream
07-27
根据引用\[1\]中的信息，报错信息是"Failed to deploy 'XXX Dockerfile: XX/XXX/docker/Dockerfile': Can't retrieve image ID from build stream"。这个错误通常是由于无法从构建流中获取镜像ID引起的。根据引用\[2...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值