I am using Ubuntu 16.04 and I want to save my host configurations. I have assigned my hosts ip addresses but when I close gns3, the configurations are discarded. How to I save configurations? Network topology

Server configuration

  • 1
    Did you do copy running-config startup-config in the switch?
    – Ron Maupin
    Sep 28, 2017 at 14:27
  • 1
    What version of the GNS3 are you running?
    – TDurden
    Sep 29, 2017 at 0:58
  • @TDurden version 2.0.3
    – theTypan
    Sep 30, 2017 at 17:48
  • @RonMaupin No, I didn't
    – theTypan
    Sep 30, 2017 at 17:49
  • If you don't save your configuration in a switch or router, then you will not have it when it starts up again.
    – Ron Maupin
    Sep 30, 2017 at 18:37

2 Answers 2


In GNS3, by default, nothing will persist after reloading your project unless your Docker Container is configured to do so. Your Docker Container may not be configured to have persistent data. This behavior is described in the official GNS3 documentation.


By default nothing is persisted on disk. The container needs to be designed for that.

If in the Dockerfile the container mount volumes. GNS3 will create in the project folders a folder for each Docker volume and will write file inside.

This mean if you use a container outside GNS3 the data will not be available. But also this mean all the data of the GNS3 project is in the same location.

Depending on your use-case, a simple work-around could be to use VPCs or the pre-built Ubuntu Docker appliance as hosts instead.


I guess your hosts are TinyCore Linux machines. TinyCore restores files -including startup scripts- from an archive and configures itself with those scripts. You should alter startup scripts and save it into the backup archive.

  • Edit /opt/bootlocal.sh and add your startup commands.

    # put other system startup commands here
    ifconfig eth0 netmask
  • Rebuild backup archive using filetool script. It creates a backup archive including files and directories listed in /opt/.filetool.lst and excluding the ones in /opt/.xfiletool.lst (/opt is already included so you don't need to edit anything.)

    filetool.sh -b
  • Just in case

  • Restart the node

Now your node should be having a persistent configuration.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.