对啊You have installed container package, first?
[admin@CHR] > /container/add remote-image=pihole/pihole:latest interface=veth1 root-dir=pihole mounts=dnsmasq_pihole,etc_pi hole envlist=pihole_envs failure: not allowed by device-mode [admin@CHR] > system/device-mode/print mode: enterprise
+1pls tell me how to enable CHR\x86 in system/device-mode/container?
/system/device-mode/updatecontainer=yes asks for a manual poweroff or reset - turn off vps via isp manager there is not working
nopeWhen you do any option, are you see "router was rebooted without proper shutdown" error at first line at log when routeros come back?
I just tested with latest VirtualBox and it works fine using the "reset" in vitualbox with the CHR 7.5 imagesSame thing to me when i tried it on VirtualBox, can not update the device-mode.
I also thought that from the management console, only a warm restart. I created a ticket with the provider and they answered me in technical support, "stop button in the console executes the virsh shutdown command"You aren't doing anything wrong. Probably when you hit stop or restart isp manager notify routeros and do it graceful reboot/shutdown.
No matter what i did, container permission given only when i force vm to stop like power off and on like hardware. That's why i ask if you see that error/information at first place.
Maybe mikrotik dev's give an exception for CHR instances at later versions since we don't have button and not everybody can hard stop vm because of permissions or incompatibility of software. =/
Anyway if i find easy way to do it, let this thread aware.
virsh destroy
/system/device-mode/update container=yes
Unfortunately it doesn't work for my vps provider...I asked the technical support of my vps provider to doCode:Select allvirsh destroy
/system/device-mode/print mode: enterprise container: yes
I just love the idea. AWS first sends the ACPI shutdown, and in few minutes, if the instance is still up will cold-stop it. And idea presumably is to make the machine "swallow" ACPI command sending that immediately after start.On AWS, after install container:
aws ec2 start-instances --instance-ids i-???
aws ec2 stop-instances --force --instance-ids i-???
I can not find any information about that only push button works, but not power cycle.
I am struggling with the same issue here. AWS support have advised that a "dirty shutdown" is not possible. Even using the force option listed in here.I just love the idea. AWS first sends the ACPI shutdown, and in few minutes, if the instance is still up will cold-stop it. And idea presumably is to make the machine "swallow" ACPI command sending that immediately after start.On AWS, after install container:
aws ec2 start-instances --instance-ids i-???
aws ec2 stop-instances --force --instance-ids i-???
Unfortunately, I couldn't replicate this on my setup. And I'm doing that just a month later so I doubt AWS changed something.
I was testing on t2.micro. Used the AWS CloudShell to minimize the lag. I also tried to add arbitrary sleeps between start and stop, tried with and without "--force" -- it just shows "Stopping" for 5-10 seconds and stops, without giving me a chance to input anything to terminal.
edv4ld0,你能分享更多细节你如何做的that?
I agree with it, I've seen many server provider not to expose all the control functions, their shutdown button will send shutdown signal instead of forcing power down, I had to give up using RouterOS on these vps servers.I have the very same issue! Mikrotik must devise a different method for enabling container on x86 or CHR platforms.Some VPS providers perform a gracefull shutdown/restart of the system no matter what. Best to change the method for CHR version...
Good afternoon. Can you suggest how you did it?Only thing that worked for me to get it working on AWS, was to launch the cloud vm as an ubuntu/debian VM, then set up the chr with container enabled on another local vm with virtualbox or whatever, ssh the image over to a ramdrive on the ubuntu CHR, and then dd the image and reboot. But beware all of this wipes the license. Oh and I'm sure there's an easier way, but I don't know it
I can confirm that this method works. However at about 2m30s in the countdown was still going and AWS had not terminated the instance. So I went to the console and issued a Force Terminate. It said it was successful. After no shutdown after 30 seconds I issued it again. Then I waited. It eventually stopped. I started and was happy to see that it was enabled. BTW, I used this guide to install v7.8 from RAW diskhttps://bookstack.bluecrow.net/books/mi ... in-aws-ec2.On AWS, after install container:
1) Stop EC2 (wait until it's stopped).
2) Using AWS CLI (one after the other):
aws ec2 start-instances --instance-ids i-???
aws ec2 stop-instances --force --instance-ids i-???
* On console in Instance state, it will be showing Stopping.
3) Connect to CHR using your favorite client, to enable the container:
/system/device-mode/update container=yes
The instance will shutdown between 3 and 4 minutes. Wait.
4) Start EC2, the log will appear:
router was rebooted without proper shutdown
* The container will be enabled.