App Submission: Mikrotik

[henriquesebastiao]

App Submission

Mikrotik

...

256x256 SVG icon

...

Gallery images

...

I have tested my app on:

• umbrelOS on a Raspberry Pi
• umbrelOS on an Umbrel Home
• umbrelOS on Linux VM

[henriquesebastiao]

Setting user: 1000:1000 in docker-compose.yml causes the network interface not to work on Mikrotik.

Log:

mikrotik_server_1  | RTNETLINK answers: Operation not permitted
mikrotik_server_1  | Cannot find device "qemubr0"
mikrotik_server_1  | touch: /var/lib/udhcpd/udhcpd.leases: Permission denied
mikrotik_server_1  | udhcpd: /routeros/dhcpd.conf: No such file or directory
mikrotik_server_1  | udhcpd: started, v1.37.0
mikrotik_server_1  | udhcpd: can't open '/var/lib/udhcpd/udhcpd.leases': No such file or directory
mikrotik_server_1  | udhcpd: socket(AF_INET,3,255): Operation not permitted
mikrotik_server_1  | qemu-system-x86_64: -hda chr-7.17.1.vdi: Could not open 'chr-7.17.1.vdi': Permission denied
mikrotik_server_1  | /routeros/bin/entrypoint.sh: line 26: /routeros/dhcpd.conf: Permission denied
mikrotik_server_1  | Failed to send flush request: Operation not permitted
mikrotik_server_1  | RTNETLINK answers: Operation not permitted
mikrotik_server_1  | Error: argument "qemubr0" is wrong: Device does not exist

[henriquesebastiao]

If relevant, information about the ports used by RouterOS can be found here:
https://help.mikrotik.com/docs/spaces/ROS/pages/103841820/Services

[github-actions]

🎉   Linting finished with no errors or warnings   🎉

Thank you for your submission! This is an automated linter that checks for common issues in pull requests to the Umbrel App Store.

Please review the linting results below and make any necessary changes to your submission.

Linting Results

Severity	File	Description
ℹ️	mikrotik/docker-compose.yml	External port mapping "8322:22": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8343:443": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8728:8728": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8291:8291": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8353:53/udp": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8353:53/tcp": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8361:161/udp": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "500:500/udp": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "4500:4500/udp": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8394:1194": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "1701:1701": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	External port mapping "8331:13231": Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️	mikrotik/docker-compose.yml	Potentially using unsafe user in service "server": The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.

Legend

Symbol	Description
❌	Error: This must be resolved before this PR can be merged.
⚠️	Warning: This is highly encouraged to be resolved, but is not strictly mandatory.
ℹ️	Info: This is just for your information.