Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[7.0.0-beta.2] docker apps not starting with assigned mac-address after reboot or array restart

  • Minor

Hi,

as the title suggest, I noticed a bug that, when starting a docker app after reboot or array restart, they won't use the mac-address predefined in "Extra Parameters".

Doesn't matter if using "--mac-address=02:42:xx:xx:xx" or "--mac-address 02:42:xx:xx:xx"

 

This is true for both linuxserver/emby and linuxserver/plex and both are connected directly to the network, with their own predefined IP and under a different VLAN than what the server is in.

Weirdly enough a third docker app (jonarin/glftpd), with the same setup (also connected directly and to the same VLAN), is not showing this symptom.

 

Haven't noticed this on any earlier release. I'm assuming it's related to the current beta.

 

Steps to reproduce:

- Stop and restart the array and/or reboot the server

- start the dockers

- they will start up perfectly fine and use the assigned IP but with a different MAC

 

Workaround to fix:

- with the array and docker running, modify anything in the template or force-update the docker app

 

 

Does anyone have an idea how to fix this?

diagnostics-20240929-2341.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.