Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can't install on Mikrotik ac3

Open
#459 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker

Research direction

Start with the linked MikroTik forum discussion, especially its last reply, and compare the successful CHR installation with the ac3 installation using usb1. Check whether the extraction stall is a supported Docker or external-drive behavior; done means identifying a reproducible cause, workaround, or confirmed compatibility limitation.

Written by the indexing model from the issue text.

Description

needs more info

Hi mates, I've troubles installing this container on Mikrotik ac3, I've used the same procedure I did succesfully on CHR (same RouterOS version 7,16), the package extracts but then keeps extracing and doing nothing, no bytes are written more to USB. I've tries also version 3.1.12 as a friend suggested me since it supports v6 processors, but same result.
What can be wrong here? Unfortunately these is no helpful log.
The main difference between installations is that on CHR I've used disk1, and here usb1, maybe this docker doesn't support installation on an external drive?
A ful discussion with all attempts done can be see here, this friend tols he was able to run it on Mikrotik ac2, that maybe has a v7 processor.
thank you for you kind support!

https://forum.mikrotik.com/viewtopic.php?p=1102316#p1102316
To don't waste time, I would suggest start reading from the last reply

Dominant language
Shell
Stars
540
Forks
434
Avg merge
24m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from node-red/node-red-docker

All issues in node-red/node-red-docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.