/16 in example is just example
It can be any routed subnet in your network or you can use nat (I do not recommend, if you do not exactly know why do you need it, it but up to you )
Hi @normis,
Curious if 7.1.1 or the release candidates for 7.2 include / will include Docker support again? Or if you guys had a specific release where it may be included again?
I guess I’m also wondering what the restrictions may be, for example if a program inside Docker could send AT commands to a cellular modem in the router? I’m essentially trying to measure WAN / cellular link quality and publish the findings over a UDP socket. Curious if that will be possible for my program inside Docker?
Best,
Philipp
Of course a container can talk to the RouterOS on the host router, and that can talk to serial ports. So it should be possible to arrange that, even without any support in Docker containers to access serial ports.
Not dismissing containers, but existing scripting language can do what you want without spinning up a container. And, while possible to arrange serial data in a container, not sure you’d be see the actual serial ports in docker. But you can redirect any RS232 serial from Mikrotik to container via /ports/remote-access so that be option, once containers are re-introduced.
If read LTE data using AT commands is your need, at-chat should get whatever you’d need.
:global lteatdata [/interface/lte/at-chat [find] input="ATI" once as-value]
We use that data in /tool/fetch in a script scheduled by /system/scheduler to store the data in AWS. In V7, the IoT package supports MQTT, so the CQI, RSRQ, or whatever AT modem data can easily go to Timeseries, DynamoDB, or whatever in AWS. But you can also use MQTT to an OSS MQTT broker on the host you want processing your cell data to avoid needing Amazon or the like. We haven’t used MQTT in production, but seems to work fine for transporting LTE/5G/cell metrics from a Mikrotik, without containers.
Thanks, pe1chl / Amm0. Mikrotik & RouterOS newbie here 
I have both modems publish debug logs (“QXDM”) on /dev/ttyUSB0 to get more fine-grained LTE packet information. Those are commonly then parsed with a QXDM tool (like QCAT), or similar. I’d essentially want grab these messages (for both modems in my RBM33G), and filter & publish to a single client connected to an Ethernet port (further processing there).
Curious if that has been realized (or should be possible), with / without Docker support.
Thanks again!
Someone ask about Quectel LTE debug in another thread, see http://forum.mikrotik.com/t/v7-2rc1-is-released/154316/1
Maybe you have some low level needs, but I’d have to imagine there is an AT command to get most data. If you looking at packet data, you can use /tool/sniffer on the LTE interface in “streaming” mode then decode TZSP with LTE packets on remote wireshark/etc. Now it be fascinating to know how well correlated Mikrotik’s packet traces are with QXDM packets traces, specifically the timing and framing – but that doesn’t sound easy.
You might want to start a new topic with more detail, this thread isn’t the best place for a QXDM discussion. Pretty sure containers aren’t going to help too much with getting/using QXDM.
Thanks, Amm0, much appreciate these pointers.
That was me in the other thread. There’s an aggregation bug on the EM160 only on AT&T that I’m trying to hunt down for Quectel. I use their QLogger app to grab the data over ethernet with the DM port exposed in 7.2rc1 and after. This puts QXDM files to disk. So I don’t think you need docker support for what you want to do. Now, I want docker support to come back for a completely different use case, but it does involve LTE stuff.
Thanks BitHaulers. Really great (and timely) to see this possible from 7.2rc* on.
Philipp
Same here.
But it’s fair enough that serial redirection directly to a future containers support probably have some IoT use cases. But in the last container release, the docker shell wasn’t available… so that seemed like a long wait for what is possible today with serial-over-ethernet. Which likely the least difficult part of any problem where QXDM be useful 
But rather see my container request for a MetaROUTER replacement before serial ports in containers
Super interesting The redirection of the QXDM logs to a Docker container (in my mind) basically boils down to running a lightweight parser / filter on those messages, before publishing them from the router to attached (ethernet) clients onward. E.g., maybe there are only specific events that need forwarding (that is the case in my scenario..). I’ll open up a separate thread once I get to the implementation bits… just wanted to make sure that this path (modem serial forward to Docker container, running parsing there, followed by publishing processed findings) is actually possible before I put deeper thought into it.
Best!
Any news about Container function? I would like to add Pihole directly to Mikrotik, because now i have to run 2 RPIs for that because one of them tends to fail from time to time and i don’t wan’t to use public DNS servers as backup in Mikrotik because then from time to time, some ads get through.
container.npk bump
looking forward for container.npk
One more.. looking for that option to run tvheadend.
I know its becoming spam at this point, so I apologize. I know mikrotik said they’re redesigning container, understandably that’ll take time. Meanwhile maybe can they include the previous container implementation in 7.2rc testing branch, its testing branch after all.
I originally placed my order for a RB5009UG based on the fact containers were in beta and be in the final 7.1 release. I’m not happy to hear it will take a long time. I can’t sell yet my old NAS to pay for the new hardware, I now regret my purchase. If I knew, I would have waited instead of being short.
@mikrotik - is there an ETA?
I’m also kinda in the same boat. I purchased RB5009 hoping to play around with containers. (no over ambitious plans like NAS thou 
). A probable good news is maybe it won’t be long before container comes back. Just noticed that I got this reply in the other thread.
I really hope containers is served soon.
I also have a rb5009 that longs for container support.
I donated my Rpi4 because i had big hopes of runing pihole as a docker on my new purchase…
Before I got it container support was gone…BIG setback there.
When container support is back, I’m also gonna kick out my old cisco 3702 AP-s and roll in some cAP AC 
Why can I not see the Container or Docker npk in any of the downloads? (even in the extra packages). I have checked both 7.1.5 and 7.2 Extra packages but it does not seem to be there. What am I doing wrong?