It's also worth noting that we've changed our Docker naming convention. This is likely an aside to your issue, but the current version of our WordPress appliance is v15.2. I would expect the second and third to be more likely scenarios, but I'm guessing. there is some uniquely broken with your set up, that for some reason only affects the TurnKey appliance.to Docker?) have broken the v14.2 TurnKey WordPress appliance or it's an issue with how GNS3 configures the TurnKey WordPress appliance and nobody has previously bothered to report it the issue or.As this is the first report of this behaviour, that would suggest to me one of 3 possibilities: It's possibly also worth noting that the v14.2 WordPress appliance was released over 18 months ago. in all other ways, does the TurnKey appliance appear to be operating as expected?! Can you access the Web front end of WordPress ok? I.e. TBH, that doesn't make a lot of sense to me. You note that other "VMs" save their settings fine and it's only the TurnKey instance that isn't. And TurnKey WordPress is running as a Docker container nested within that. So I would assume that GNS3 is based on some Linux distro which itself has Docker installed (which is the software that Docker containers run within somewhat akin to VMware being software that VMs can run within). So judging from what you say, plus your screenshots, it looks like GNS3 itself is running inside VMware. As you note (at least for your purposes) Docker is something akin to a VM (TBH only vaguely in reality, but for your purposes the differences are semantic). Judging from that, GNS3 is using our Docker build. Unfortunately, the download link on the GNS3 doc page you posted is broken (I get a message "Downloads can only be accessed from main site"), but decyphering the HTML encoding, leads me to. Thanks for the extra info, but TBH, I'm still not clear what might be the cause of your issue?! If you're not sure, please just post the full output of "turnkey-version" (from the commandline within TurnKey). It might also be useful to clarify the version of TurnKey you are using. The only other thing that I can think of is if perhaps you aren't completing the initial "firstboot" scripts via commandline/SSH? Although I still wouldn't expect filesystem changes that you've made to be wiped out by that. When you say "When I log into the web interface and look at file system the right hand column all says not saved", I'm not quite clear what you are referring to?! Do you mean the filemanager within Webmin? Or something else? Perhaps a screenshot might assist there? Your experience would be expected within that context, but it should be obvious if that's what's happening and I'm guessing that's not what is going on here? (But perhaps?!) Our ISO builds have a "live" mode which runs the OS from RAM rather than installed to the filesystem. Notwithstanding that info, your experience is certainly not expected behaviour! At least not in any of our default builds, with the notable exception of our ISO build running "live". TBH, I'm unfamiliar with GNS3?! I just googled it and now have a little idea about it, but am still a little unclear on exactly how it relates to TurnKey and/or how you are installing TurnKey within GNS3 (assuming I understand correctly)?! Could you please give a little more context and/or point me towards some further info on that? Especially which TurnKey build type is being used in this scenario.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |