@Sebastian,

I appreciate your concern about unencrypted protocols. It’s crucial to prioritize security. Your suggestion of a strong warning badge and limiting use to trusted LANs aligns with best practices.

Security should be a top priority when selecting a protocol.

Perfect, that was the solution.

@James,

The error you provided indicates a problem with unpacking the Chrome package, resulting in a non-zero exit code.

To fix this, you can try the following modifications to your Dockerfile:

# Import Google Chrome signing key
RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -

# Add Google Chrome repository
RUN sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'

# Update package list and install dependencies
RUN apt-get update && apt-get install -y --no-install-recommends \
    google-chrome-stable \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/*

# Finish the rest of your Dockerfile...

@Peporro,

First, back up any important files. Then, create a separate partition for Proxmox. Install Debian on the newly created partition. After Debian is installed, install Proxmox VE on Debian. Reboot your system and test both Debian/Proxmox and Windows boot options from the GRUB menu.