when restart a container created by its template, is takes a different IP than old one

[Pishoy]

• need to make zerotier ip configuration is fixed even the container got restarted

[zaibon]

Can you please give out the full data used to create your service as well as the flow used to test. Cause we already save the zerotier identity of a container exactly for this reason.

[PeterNashaat]

• yes that happens.
• you need to use the host portforward to the container not the container ip, as the portforward is persistent even if the container is rebooted.

[Pishoy]

yes i did that , thanks Peter @zaibon here is the stpes:

• create container with below data

      'flist': 'https://hub.grid.tf/tf-autobuilder/threefoldgrid-freeflow-autostart-master-213866b730.flist',
      'mounts': [{'source': humhub_dir, 'target': '/var/www/html/ffp'},
                 {'source': mysql_dir, 'target': '/var/lib/mysql/'},
                 {'source': authkeys_dir, 'target': '/root/.ssh/'}],
      'nics': [{'type': 'default'},
               {'type': 'zerotier', 'name': 'zerotier', 'id': ztid, 'ztClient': 'ztclientB'}],
      'ports': ['{0}:80'.format(http_port), '{0}:22'.format(ssh_port)]}

  • after create it get the zerotier_ip by zerotier_client
  • terminate the container
  • check the zerotier_ip again, will get a different zerotier_ip

    node

    in KDS farm , ip 10.102.178.130

    jumpscale

    development_960