You can reach both WinBoat and Docker support teams directly, and each offers different channels depending on the type of issue you want to report. Since you're documenting a complex “Windows‑on‑Linux‑via‑Docker” workflow and encountering install‑time behavior, UI latency, and application‑layer failures (Reolink client, JavaScript errors, VNC responsiveness), the right contact path depends on which layer you want to report the issue to. 🛠 WinBoat (WinBoat / WinBoatOS / WinBoat VM) — How to Contact Support WinBoat provides two official support channels: 1. Direct Technical Support Email support@winboats.com This is their designated address for technical issues. 2. Support Ticket Portal They provide a full support ticket form for reporting installation problems, VM behavior, Docker‑related issues, and runtime bugs. You can submit a ticket through their “Get Support” page. 3. Phone Support (if needed) Product Support: 706‑471‑1130 Sales (if you need account‑level help): 770‑680‑3200 These channels are appropriate for: VM install failures (Windows 10/11 image issues, RAM allocation warnings) Unexpected Docker‑layer behavior during WinBoat setup VNC interface slowness or missing desktop rendering JavaScript/UI errors inside the WinBoat browser interface Feature requests (e.g., “show install progress logs”, “exportable error text”) 🐳 Docker — Where to Report Docker‑Layer Issues If you suspect the issue is at the Docker Desktop or container‑runtime level (e.g., virtualization, resource allocation, container performance), Docker offers several support paths. 1. Official Docker Support Portal Docker’s “Contact Support” page allows you to submit issues directly. 2. Docker Desktop Troubleshooting & Support Their support documentation outlines what is supported and how to get help. This includes: Installation crashes Virtualization/BIOS issues Desktop not launching Performance issues Container runtime problems 3. Community Support Channels These are useful if you want to compare behavior with other Linux Mint or low‑RAM Docker users: Docker Community Forums Docker Community Slack GitHub repos for Docker Desktop (Linux/Mac/Windows) 4. General Contact Page Docker’s main contact page also links to support, documentation, and subscription options. 🧭 Which Team Should You Report Each Issue To? WinBoat Support (Primary) Use WinBoat support when the issue involves: Windows image install failures inside WinBoat RAM allocation warnings during WinBoat VM creation Missing or slow Windows desktop rendering in the browser VNC WinBoat’s internal UI (JavaScript errors, missing logs, slow app loading) Reolink client behavior inside the WinBoat environment Docker Support (Secondary) Use Docker support when the issue involves: Docker Desktop installation on Linux Mint Virtualization support (BIOS, KVM, QEMU, cgroups) Container performance (CPU/RAM starvation) Networking issues between host ↔ container Docker engine errors during WinBoat container creation 🧩 A Practical Messaging Strategy for Your “WinBoat Lessons Learned” Project Given your goals—documenting Windows‑to‑Linux transitions, building a reproducible toolkit, and reporting issues cleanly—here’s a workflow that will help you communicate effectively with both teams: 1. Capture Logs and Errors in Text Form Since Mint’s screenshot tool didn’t capture the JS errors: Use Ctrl+Shift+I in the WinBoat browser tab to open Developer Tools (if available) Copy console output into a text file Or run docker logs to capture backend logs 2. Separate Issues by Layer Create two text files: winboat_issues.txt — UI, VM, Windows image, Reolink client behavior docker_layer_issues.txt — virtualization, resource allocation, container performance 3. Attach These to Support Tickets Both WinBoat and Docker accept attachments in their ticket systems. 4. Add Your “Lessons Learned” to Your Web Server Your http://iii.thruhere.net site is a perfect place to host: Install logs Step‑by‑step reproduction notes Screenshots Workarounds Cross‑platform comparisons This will also help support teams understand your environment. 🔍 One question to help you move forward Do you want help drafting a single combined issue report that you can send to both WinBoat and Docker, or would you prefer two separate reports, each tailored to the correct team? ==================== ===================== =========================== ====================== ============================== give me both.. ' in case '. help drafting a single combined issue report that you can send to both WinBoat and Docker, or would you prefer two separate reports, each tailored to the correct team? You can absolutely have both: a single combined report that covers the entire WinBoat‑on‑Docker‑on‑Mint workflow, and two separate, targeted reports—one for WinBoat, one for Docker—each tuned to the correct layer of responsibility. The combined report is ideal for your Lessons Learned / Windows‑to‑Linux documentation and for giving both teams a unified view of the environment. The two tailored reports are ideal for actually submitting issues to each support team. Below is a complete, technician‑grade structure for all three deliverables, aligned with your documentation style, your reproducibility goals, and your preference for clean, investigator‑ready reporting. 🧩 When to Use a Combined Report vs. Separate Reports Combined Report — Best for: Showing the full chain: BIOS → Mint → Docker → WinBoat → Windows image → Reolink client Demonstrating how issues cascade across layers Hosting on your iii.thruhere.net site as part of your Lessons Learned series Giving both teams a single, coherent narrative of what you attempted and why Separate Reports — Best for: Submitting actionable tickets to each team Avoiding cross‑layer confusion Ensuring each team sees only the issues they own Attaching logs specific to their component 📝 Combined Issue Report (Full Workflow) This is the version you can publish on your site and attach to both support teams. Title: WinBoat on Docker on Linux Mint (8 GB RAM HP ThinkPad) — Installation Behavior, Performance, and Application‑Layer Issues Environment Summary Hardware: HP ThinkPad, 8 GB RAM, 1 TB SSD Host OS: Linux Mint BIOS: Virtualization enabled per WinBoat pre‑install guidance Docker: First‑time installation and use WinBoat: Attempted Windows 11 Pro image → failed; Windows 10 Pro image → succeeded Goal: Run Windows‑only Reolink Client (21+ cameras) after Wine/Bottles failed Observed Issues Across the Stack RAM allocation warnings when attempting Windows 11 image (4 GB recommended, 2 GB required to proceed) Windows 11 install failed even after reducing RAM Windows 10 install succeeded, but: Browser‑based VNC interface extremely slow No standalone Windows desktop visible outside browser tabs Long delay before Windows apps populated No visible progress indicators during install Reolink Client folder‑copy attempt triggered: Multiple JavaScript errors Hidden error window behind UI No text‑copyable error output Linux Mint screenshot tool unable to capture the JS error window Reolink Client installer not yet tested inside WinBoat Desired improvement: Text‑based error logs or exportable console output for reporting Logs and Evidence Docker logs (attach) WinBoat browser console logs (attach) Notes from JS error window (manually transcribed) Steps to reproduce (attach) Impact Unable to validate WinBoat as a Windows‑compatibility layer for Reolink Client Difficult to troubleshoot due to lack of text‑based error output Performance issues limit usability on 8 GB RAM systems Requested Clarifications Expected RAM minimum for Windows 10/11 images Whether browser‑only VNC interface is expected behavior Whether a native desktop viewer exists Whether Reolink Client is known to work inside WinBoat Whether JS error logs can be exported in text form 🛠 WinBoat‑Specific Report (Targeted Ticket) Subject: WinBoat Windows 10/11 Install Behavior, VNC Performance, and JavaScript Errors (Linux Mint + Docker) Issues to Report RAM allocation warnings and Windows 11 install failure Windows 10 install success but: No desktop outside browser VNC Very slow VNC responsiveness Long delay before apps appear Reolink Client folder‑copy attempt triggers JS errors No text‑copyable error logs Need for progress indicators during install Attachments WinBoat browser console logs Screenshots (if any) Steps to reproduce Contact Paths Email: support@winboats.com Support Portal: WinBoat “Get Support” page Phone: Product Support: 706‑471‑1130 Sales: 770‑680‑3200 🐳 Docker‑Specific Report (Targeted Ticket) Subject: Docker Runtime Performance and Resource Allocation Behavior During WinBoat VM Creation (Linux Mint) Issues to Report RAM allocation behavior during VM creation Container performance on 8 GB RAM system VNC responsiveness possibly tied to container resource limits Any Docker engine warnings during WinBoat install Request for guidance on optimal Docker settings for WinBoat Attachments docker logs System info Steps to reproduce Contact Paths Docker Support Portal Docker Desktop Troubleshooting Docker Community Forums / Slack Docker GitHub repos (Desktop + Engine) 📦 How This Fits Your Lessons‑Learned Webpage Your combined report becomes the anchor document for your new sub‑page: BIOS prep Mint setup Docker install WinBoat install attempts Reolink testing JS error behavior Screenshots, logs, and reproducible steps Recommendations for other technicians migrating from Windows → Linux This aligns perfectly with your goals of: reproducibility technician‑grade clarity cross‑platform onboarding evidence‑ready documentation If you want, I can now generate all three reports in polished, ready‑to‑send text form, or I can help you refine them for your website’s formatting style.