Hi There, Exact Same Problem here.
in VM Manager Stop/Start or Restart doesn’t work and the container never turns on. any recommend? tnx
On DigitalOcean “Power cycle” option worked.
I am running into this issue on v7.12.1 on a t2.nano instance @ us-east-2 (AWS). The provided tricks previously posted in this thread have not worked out for me. Just to avoid covering the same ground twice, I can confirm that I have the container package installed and have tried the awscli trick to no avail.
Does anyone know if there is another way to emulate the reset button on AWS?
Is there a third option not in your screenshot? I’ve had to try them all, one at a time, on various cloud platforms, to get it to work..
Otherwise, extend the timeout way past 5 minutes and open a ticket for the provider to do it for you..
You need a power-off/reset without shutdown.. If it was a normal PC, would be holding the power button for 4 seconds to power off rather than pressing once to let it shutdown normally..
I was able to get device-mode set on AWS using a more reliable method than waiting on awscli to flake out. The idea is to create a snapshot of the instance during the 5 minute period and then to forcibly replace the running disk with the newly created snapshot, all from within the AWS web interface. I am sure you could automate this with awscli but I figure this would provide a simple way for users wanting to fully utilize RouterOS/CHR on AWS.
Optional
Create RouterOS AMI using the following guide: https://bookstack.bluecrow.net/books/mikrotik/page/creating-a-chr-instance-in-aws-ec2
- Locate the Volume ID of your CHR by going to your AWS EC2 Console and navigating to Instances > Storage and locating the Volume ID near the bottom of the page
- Install container package and update the device-mode using the following command and stay logged into the CHR:
/system device-mode update container=yes
- Go to your AWS EC2 console and go to Snapshots, from there you will need to create a snapshot of the volume that you grabbed in step 1. Give it a memorable name.
- Go back to Instances, select your instance, and on the top right go to Actions > Monitor and Troubleshoot > Replace Root Volume
- You are going to choose Snapshot in the list of options and then select the snapshot from the list, you should be able to find it quickly by using the memorable name.
- You will notice that you will be kicked out of your session with the CHR. You will need to reboot the instance from the console at this point.
This allowed me to run containers on my AWS CHR, so hopefully it will work for others that run into this snag.
Azure VM container enabling:
- VM control panel open “serial console”
- press power button
- select “reset VM (hard)”
Run a CHR in the local virtualization environment and enable the container, then package it and dd on the vps.
This is a proven and workable solution.
The most important thing is that this method is suitable for almost all cloud servers !!
If necessary contact me
Could you please provide a step-by-step explanation on how to “then package it and dd on the VPS”?
Thank you!
To put it simply, it means saving a copy of the local disk image with the container environment enabled, and then dd it to the vps
WORKED LIKE A CHARM!!! I had tried rebooting, stopping the EC2 instance with no luck. Install the containers x84 package, and run in the virtual CHR the command after rebooting:
/system device-mode update container=yes
within the 5 minutes make a snapshot of the running instance (it sometimes takes a while but less than the 5 min), replace the root and reboot the instance in the EC2 console!!! I would guess you need to do all this in less than the 5 min or at least the snapshop has to be taken in less than the 5 min. Do backup the server before hand. I have had a CHR not boot after a hard reset!!