问题描述
我在ServerFault上尝试了此问题，但没有响应，请在此处尝试:
I tried this question on ServerFault, no response yet, trying here:
我在实例上安装了Tomcat8，并配置了重新启动时的启动.从该实例创建了一个AMI.现在我看到了:
I have Tomcat8 installed on my instance with startup on reboot configured. Created an AMI from this instance. Now I see:
1)再次安装了Tomcat(我可以确认这一点，因为我已经从webapps文件夹中删除了不必要的webapp.这些不必要的战争在我的原始实例上不存在.)
1) Tomcat was installed again (I can confirm this because, I have removed unnecessary webapps from webapps folder. These unnecessary wars are not there on my original instance).
2)Tomcat默认情况下未启动(我认为这可能是由于我重新启动配置中的启动搞砸了).
2) Tomcat is not started by default (I think this could be due to that my start on reboot configuration is messed up).
有趣的是，我的自定义war文件仍然存在.有没有人观察到这个?关于如何克服这个问题并且不进行全新安装的任何建议?
Interestingly my custom war file is still there. Did anyone observe this? any suggestion on how I can overcome this and not do a fresh install?
推荐答案
我想我已经解决了这个问题. yum.conf(位于/etc/下)具有名为"releasever"的设置，默认情况下为"latest".
I think I figured out the issue. yum.conf (which is under /etc/) has a setting called "releasever" which by default is "latest".
基于yum.conf文件中的注释
似乎几天前发布了新版本以供回购&由于启用了此"latest"配置，因此AMI在创建实例时拉动了较新版本的Tomcat.
It seems there is newer version published to repo few days ago & due to this "latest" configuration enabled, AMI pulling newer version of Tomcat while creating instance.
这篇关于从自定义AMI创建实例时将重新安装Tomcat8的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！