Containers • Re: how enable container on CHR\x86?

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/mi ... in-aws-ec2

1. 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
2. Install container package and update the device-mode using the following command and stay logged into the CHR:3. 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.
4. Go back to Instances, select your instance, and on the top right go to Actions > Monitor and Troubleshoot > Replace Root Volume
5. 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.
6. 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.

Statistics: Posted by krosseyed — Sun Feb 25, 2024 4:34 am

---