Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
You cannot install native Home Assistant Add-ons (now called Apps) in a Home Assistant Container deployment managed by Docker Compose. Native Apps are installed and supervised by the Home Assistant Supervisor, and the Container installation has no Supervisor. The Compose replacement is to run the underlying service as its own container, then connect Home Assistant to it through the service’s supported integration or protocol.
If you need the built-in Apps store, Supervisor-managed backups and updates, and appliance-style operation, install Home Assistant OS instead. Choose Container plus Compose when you deliberately want to maintain the Linux host, Docker, networks, images, permissions, backups, and upgrades yourself.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat “add-ons” mean in each Home Assistant installation
Home Assistant uses the term App for what many users still call an add-on. An App is a containerized service that the Supervisor installs, configures, starts, updates, and includes in its management model. Examples include an MQTT broker or Samba file sharing. The Supervisor itself runs Home Assistant Core, manages backups, and controls those App containers.
A Home Assistant Container installation runs only Home Assistant Core in a container. Docker Compose can start additional containers, but Compose does not become a Supervisor and cannot add the Apps store to the Home Assistant interface. The Home Assistant FAQ states: “Home Assistant Container does not support apps, and you are responsible for updates and the host operating system.”
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
That distinction is architectural, not a missing menu setting. Installing a different Compose label, adding a privileged flag, or mounting the Docker socket does not turn a Container installation into a Supervisor-based system.
Home Assistant OS versus Container plus Compose
Use the following comparison before changing an existing installation. It separates features provided by the operating system from services you must operate yourself.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Capability | Home Assistant OS | Home Assistant Container with Compose |
|---|---|---|
| Native Apps/Add-ons store | Supported through the Supervisor. | Not supported; run equivalent services as separate containers. |
| Supervisor | Included and manages Core, Apps, and related lifecycle tasks. | Not included. |
| Backups | Supervisor can manage Home Assistant backups and App data as part of its workflow. | You must back up /config and every auxiliary container’s data separately. |
| Operating-system maintenance | The appliance image supplies and updates the host operating system. | You maintain the Linux host, Docker Engine, storage, security updates, and reboots. |
| Images, networks, and ports | Supervisor chooses and manages most App details. | You choose image tags, Compose networks, bind mounts, published ports, and restart policies. |
| Hardware and host integration | Supported integrations are packaged for the appliance model. | You must map USB devices, permissions, D-Bus access, and other host resources yourself. |
| Operational complexity | Lower for users who want an integrated appliance. | Higher, but with more control for people already operating Docker. |
The official installation guidance recommends Home Assistant OS for most users. Container is intended for people who already run Docker and want control of the host and containers.
What the Compose replacement architecture looks like
Keep Home Assistant Core as one Compose service. Run each former App function as another service, with its own image, configuration, persistent storage, credentials, logs, and upgrade process. Connect the services over an intentional Compose network and configure the corresponding Home Assistant integration.
For example, an MQTT App becomes an MQTT broker container plus Home Assistant’s MQTT integration. A Samba App becomes a separately managed Samba service, with access limited to the directories that need to be shared. A file editor becomes an independently managed editor container, if you can find an image that meets your security and maintenance requirements.
This is a conceptual mapping, not a guarantee that an App image can be copied unchanged. Some Apps rely on Supervisor APIs, host devices, D-Bus, privileged operations, or operating-system services. Those dependencies may require additional engineering or make Home Assistant OS the practical choice.
Free tools Windows power users keep installed
One-click scans. No signup required.
Requirements and preparation
Before creating containers, make sure the host and the service design are ready:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
- A supported Linux host with Docker Engine and the Docker Compose plugin installed.
- A fixed location for Home Assistant’s configuration, such as
/srv/homeassistant/config, and a separate persistent directory for each auxiliary service. - A documented plan for image tags, credentials, ports, networks, restart behavior, and upgrades.
- Enough storage for Home Assistant, service data, logs, and backups.
- A backup destination that is not the same disk as the live containers.
- Any required USB devices, host directories, or kernel permissions identified before deployment.
Do not expose every service to the LAN by habit. Internal traffic can stay on a private Compose network; publish only ports that genuinely need access from another machine.
Build a Compose project with Home Assistant and an MQTT broker
The following example shows the pattern rather than a universal production configuration. It keeps the broker private to the Compose network by using expose instead of publishing port 1883 to the host. Verify the current configuration requirements for the image you select before deploying it.
services:
homeassistant:
container_name: homeassistant
image: ghcr.io/home-assistant/home-assistant:stable
volumes:
- /srv/homeassistant/config:/config
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
ports:
- '8123:8123'
networks:
- ha
mosquitto:
container_name: mosquitto
image: eclipse-mosquitto:2
volumes:
- /srv/homeassistant/mosquitto/config:/mosquitto/config
- /srv/homeassistant/mosquitto/data:/mosquitto/data
- /srv/homeassistant/mosquitto/log:/mosquitto/log
restart: unless-stopped
expose:
- '1883'
networks:
- ha
networks:
ha:
driver: bridgeCreate the directories before starting the project:
sudo mkdir -p /srv/homeassistant/config
sudo mkdir -p /srv/homeassistant/mosquitto/config
sudo mkdir -p /srv/homeassistant/mosquitto/data
sudo mkdir -p /srv/homeassistant/mosquitto/logThe broker also needs a configuration file and an authenticated account. A minimal Mosquitto configuration commonly enables persistence, listens on port 1883, disables anonymous access, and points to a password file:
listener 1883
allow_anonymous false
password_file /mosquitto/config/password_file
persistence trueCreate the password file using the broker image’s documented password utility, then protect the file so ordinary host users cannot read it. Do not place a broker password directly in a public Compose file or commit it to source control.
Save the Compose definition as compose.yaml, then start it:
docker compose up -dCheck that both containers are running and inspect logs before configuring Home Assistant:
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
docker compose ps
docker compose logs --tail=100 homeassistant
docker compose logs --tail=100 mosquittoConnect Home Assistant to the replacement service
When both containers are on the same Compose network, use the Compose service name as the internal hostname. For the example above, the broker hostname is mosquitto, not localhost. Inside the Home Assistant container, localhost refers to Home Assistant itself.
- Open Home Assistant and go to Settings.
- Select Devices & services.
- Choose Add Integration and search for MQTT.
- Enter
mosquittoas the broker address and1883as the port. - Enter the broker account created in the password file.
- Save the integration and publish a test message from a client that uses the same broker credentials.
If another machine on your LAN must connect directly to the broker, publish the port explicitly, for example 1883:1883, and restrict firewall access to the required networks. An exposed administrative or unauthenticated broker is a serious security risk.
Replacing common Apps safely
MQTT broker
Run a maintained MQTT broker image with persistent configuration, data, and logs. Keep it on the same Compose network as Home Assistant and use the broker’s service name for the integration. If external devices connect from the LAN, publish only the broker port and require authentication. Back up the broker’s data and password file along with Home Assistant’s configuration.
Samba or network file sharing
Run a separately maintained Samba container and map only the directories that must be shared. A read-only bind mount is safer for directories that clients only need to browse. If clients must write files, map a narrowly scoped directory instead of the entire host filesystem or Docker socket.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
File-sharing permissions are controlled by the container’s users, the host filesystem ownership, and Samba’s own account database. Test from a second machine, verify that writes land in the intended directory, and confirm that Home Assistant configuration files are not unintentionally exposed to every network user.
File editors and web administration tools
A web editor with access to /config can modify automations, scripts, and secrets. Treat it as an administrative interface: place it behind authentication, avoid publishing it to the internet, and mount only the directory it needs. A container that requires broad host access, Docker-socket access, or privileged mode deserves extra scrutiny; the convenience may not justify the attack surface.
Apps with host or Supervisor dependencies
Some services are more than ordinary network daemons. If an App expects Supervisor APIs, D-Bus, a host service manager, kernel modules, USB radios, or privileged device access, a simple Compose service may fail even when the image starts. Read the service documentation for required devices, capabilities, environment variables, and filesystem paths. If those requirements are tightly coupled to the Home Assistant appliance, use Home Assistant OS instead of forcing an unsupported port.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Give every service durable storage
Containers are replaceable; their data must not be. Bind-mount each service’s documented data and configuration directories to host paths or use named volumes that you can identify and back up. Never assume that recreating a container preserves files written only to its writable layer.
- Keep Home Assistant’s
/configon persistent storage. - Keep broker databases, retained messages, credentials, and logs in the broker’s persistent directories.
- Record the host path, container path, owner, group, and read/write requirement for every mount.
- Do not mount an entire host filesystem when a single directory is sufficient.
- Test a restore on a separate Compose project so a backup is proven usable rather than merely present.
Networking and port decisions
Compose service names provide stable internal DNS as long as the services share a network. Prefer internal connections for Home Assistant-to-service traffic. Publishing a port creates a host-level listener that may be reachable from other networks, depending on firewall rules.
Use a deliberate port plan:
- Publish Home Assistant’s web port when users need to reach the dashboard.
- Use
exposeor no host mapping for services used only by Home Assistant. - Publish a service port only when LAN devices or another host must connect directly.
- Check for collisions with existing services before starting Compose.
- Protect every published administration endpoint with authentication and network controls.
Changing a service name, network, port, or credential requires updating the Home Assistant integration. A container can be healthy while the integration is still pointing at an old hostname or port.
Updates, backups, and lifecycle management
In a Container installation, you own the update sequence. The documented Home Assistant update flow is:
docker compose pull homeassistant
docker compose up -dRun the equivalent pull and recreate process for each auxiliary service according to that project’s release instructions. Pulling an image does not automatically recreate a running container with the new image; docker compose up -d performs the replacement when the image digest changed.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Before an upgrade:
- Read the release notes for Home Assistant and every service being changed.
- Back up Home Assistant’s
/configand each service’s persistent data, including credentials and databases. - Confirm that the Compose file, image tags, environment variables, mounts, devices, and ports are recorded.
- Pull the selected images and recreate one service at a time when practical.
- Check logs and the Home Assistant integration after each change.
- Test automations, retained MQTT messages, file shares, and hardware devices.
Using a floating tag such as latest trades convenience for surprise changes. Pin a deliberate version or digest when predictable upgrades matter, and update it deliberately after reviewing release notes. The stable tag in the example is convenient but still represents a moving choice.
Hardware and permissions
USB radios, serial adapters, cameras, and other host devices do not automatically appear inside a Compose container. Identify the device path on the host, map it to the service that needs it, and grant only the required permissions. Device names can change after host reboots or hardware changes, so verify mappings after maintenance.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Bind mounts can fail with “permission denied” even when the path exists. Check the numeric user and group used inside the service image, the ownership of the host directory, and any host security policy such as SELinux or AppArmor. Changing a directory to world-writable may hide the symptom while creating a larger security problem; prefer matching ownership or using the image’s documented user settings.
Troubleshooting common failures
The Apps or Add-ons menu is missing
This is expected in Home Assistant Container. The menu is provided by the Supervisor, which is present in Home Assistant OS and other Supervisor-based installations, not in a plain Compose deployment. Run the needed service separately or migrate to Home Assistant OS.
Home Assistant cannot connect to the broker
Confirm that both services are on the same Compose network, that the broker is listening on the expected port, and that the integration uses mosquitto rather than localhost. Check credentials, broker logs, and the result of docker compose ps. If the broker is intentionally on another host, use that host’s reachable address and firewall rules instead of the Compose service name.
Data disappeared after recreating a container
Inspect the service definition with docker compose config and verify that the intended host path or named volume is mounted at the image’s documented data directory. Recover from the last known-good backup before experimenting further.
A port will not bind
Another process may already own the host port. Change the host-side port, stop the conflicting process, or keep the service private with an internal network. Remember to update the Home Assistant integration if the reachable port changes.
An App image starts but does not function
Starting a container proves only that its entrypoint ran. Review required environment variables, devices, capabilities, D-Bus sockets, host paths, and Supervisor APIs. If the service depends on appliance-only functionality, stop investing in a fragile Compose workaround and use Home Assistant OS.
An upgrade breaks an integration
Check release notes, compare the old and new image tags, inspect both containers’ logs, and verify that names, ports, credentials, and file permissions did not change. Restore the previous image tag and data backup if the service is not recoverable, then test the upgrade in a separate project.
When Home Assistant OS is the better answer
Choose Home Assistant OS when the Apps store is a requirement, when you want Supervisor-managed backups and lifecycle operations, or when an App depends on host integration that you do not want to engineer yourself. It is the simpler path for an appliance-style installation and is the platform used by official hardware such as Home Assistant Green.
Stay with Container plus Compose when you are comfortable maintaining Linux and Docker, need explicit control over images and networks, or already operate several services on the host. The trade-off is permanent ownership of updates, security, storage, permissions, backups, and recovery.
Supervisor App development is a separate case
If you are building your own Supervisor App rather than replacing an App with Compose, note a version-sensitive change: Supervisor 2026.04.0 stopped supplying a default BUILD_FROM argument during App builds. App developers must specify an explicit base image, and pinned base-image versions are recommended for reproducible builds. This change affects Supervisor App development; it does not add App support to ordinary Home Assistant Container installations.
Recommended Free Tools
Quick Recap
Operational checklist
- Confirm that the desired function has a maintained container image and documented Compose requirements.
- Keep Home Assistant Core and each auxiliary service in explicit Compose services.
- Use a private network for internal traffic and publish only required ports.
- Use service names for internal connections, not
localhost. - Persist configuration and data outside the container writable layer.
- Record image tags, paths, credentials, ports, devices, and permissions.
- Back up
/configand every auxiliary service before upgrades. - Pull and recreate containers deliberately, then test integrations and automations.
- Monitor logs for Home Assistant and every replacement service.
- Migrate to Home Assistant OS when Supervisor-managed Apps or host-coupled functionality is essential.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
