To be very honest, I'm not 100% sure this is the correct place to race this issue, but as far as I understood the cloudformation templates provided at [1] , they use this chef recipes to install nexus on a ec2 instance.
The issue is quite simple:
install nexus via cloudformation template (described at [1])
check nexus is correctly up and running
stop the EC2 instance running nexus
start the EC2 instance you just stopped
check if nexus comes up again -> no, nexus is not coming online again
I would expect nexus to come up and running with no data lost again. I did experience a similar issue before with an other tool (jenkins) the simple solution was to start docker with --restart=always.
To be very honest, I'm not 100% sure this is the correct place to race this issue, but as far as I understood the cloudformation templates provided at [1] , they use this chef recipes to install nexus on a ec2 instance.
The issue is quite simple:
I would expect nexus to come up and running with no data lost again. I did experience a similar issue before with an other tool (jenkins) the simple solution was to start docker with
--restart=always.[1] https://help.sonatype.com/integrations/cloud-deployments/cloudformation---repository-manager