how enable container on CHR\x86?

hi!
pls 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


[admin@CHR] > system/device-mode/print
mode: enterprise
[admin@CHR] > /system/device-mode/update container=yes
update: please activate by turning power off or pressing reset or mode button in 4m33s
– [Q quit|D dump|C-z pause]


thx

You have installed container package, first?

yeap
I see container menu, but it gives an error.

[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

+1
I am also unable to change device-mode on my CHR. Turn off or reboot vds over VMmanager is not working for me. Container package is installed.

after issue command;
/system/device-mode/update container=yes

do not shutdown or reboot at routeros. power off vm directly.

m8, Im shutting down my virtual machine in isp manager via “restart” and “stop” buttons
without any effect.
its very strange, thats why I created this topic here
111.png
anyway thanks for the answer! i hope dev will pay attention to this problem, or they will tell me in detail where im wrong

When you do any option, are you see “router was rebooted without proper shutdown” error at first line at log when routeros come back?

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

loss license is catastrophic, thank you, but its not my way

I know it probably dosent help your exact problem but I had the exact same issue on Linode.com instances, so I hope this helps someone in the same situation.

The fix was after entering the /system/device-mode/update container=yes then going into the LISH console then issuing a CTL+A then D to exit from the running vm console to the lish submenu, issuing the “destroy” command then finnally the “boot” command.

However you might be able to issue a SysRq B comand, so look that up maybe?

In AWS you’ll need to get on the CLI and issue a force stop “aws ec2 stop-instances --force --instance-ids i-xxxxxxxxx”. I’ll see if I can do it now on my AWS instances and update this post.

nope
logs empty

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.

Same thing to me when i tried it on VirtualBox, can not update the device-mode.

I just tested with latest VirtualBox and it works fine using the “reset” in vitualbox with the CHR 7.5 images

Correction. After reinstalling VirtualBox worked ok! Thanks

Hello i have the latest Virtualbox, and tried from the VM Menu–>Machine -->Reset.

But the mode did not update to container.

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”

If its virsh then a “virsh destroy” need to be issued. this is the command that initiates an immediate ungraceful shutdown and stops the specified guest virtual machine https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-virsh-delete

thnx !
your answer helped

I asked the technical support of my vps provider to do

virsh destroy

on the hypervisor to my VM

/system/device-mode/update container=yes

and rearm from console my VM
after hard reset it and everything worked out!

please mark this answer as solved
thank you all for your help and advice

Unfortunately it doesn’t work for my vps provider…

Dear mikrotik developers, please add the ability to change device-mode easier especially for chr

the methods to enable containers are a little harsh but the security implications are pretty wild so you’re not going to get very far with support on this one.