ADS integration Exec format error on latest docker
See original GitHub issueThe problem
When starting the latest docker on a raspberry pi 4 the ADS integration seems to be broken, sounds like a build problem targeting the wrong architecture.
I’ve had a couple of issues (like MySql 8 suddenly requiring the mysql_native_password plugin instead of the previously already working caching_sha2_password) which I was able to work around but this one is blocking for me as it completely breaks the integration with my Beckhoff which is at the heart of my home control.
Labels provided through this image are:
"io.hass.arch": "armv7",
"io.hass.base.arch": "armv7",
"io.hass.base.image": "homeassistant/armv7-base:3.16",
"io.hass.base.name": "python",
"io.hass.base.version": "2022.06.0",
"io.hass.machine": "raspberrypi4",
"io.hass.type": "core",
"io.hass.version": "2022.7.0.dev20220627",
"org.opencontainers.image.authors": "The Home Assistant Authors",
"org.opencontainers.image.created": "2022-06-27 03:32:54+00:00",
"org.opencontainers.image.description": "Open-source home automation platform running on Python 3",
"org.opencontainers.image.documentation": "https://www.home-assistant.io/docs/",
"org.opencontainers.image.licenses": "Apache License 2.0",
"org.opencontainers.image.source": "https://github.com/home-assistant/core",
"org.opencontainers.image.title": "Home Assistant",
"org.opencontainers.image.url": "https://www.home-assistant.io/",
"org.opencontainers.image.version": "2022.7.0.dev20220627"
Labels of the image that is still working for me:
"io.hass.arch": "armv7",
"io.hass.base.arch": "armv7",
"io.hass.base.image": "homeassistant/armv7-base:3.14",
"io.hass.base.name": "python",
"io.hass.base.version": "2022.02.0",
"io.hass.machine": "raspberrypi4",
"io.hass.type": "core",
"io.hass.version": "2022.6.0.dev20220506",
"org.opencontainers.image.authors": "The Home Assistant Authors",
"org.opencontainers.image.created": "2022-05-06 03:33:40+00:00",
"org.opencontainers.image.description": "Open-source home automation platform running on Python 3",
"org.opencontainers.image.documentation": "https://www.home-assistant.io/docs/",
"org.opencontainers.image.licenses": "Apache License 2.0",
"org.opencontainers.image.source": "https://github.com/home-assistant/core",
"org.opencontainers.image.title": "Home Assistant",
"org.opencontainers.image.url": "https://www.home-assistant.io/",
"org.opencontainers.image.version": "2022.6.0.dev20220506"
What version of Home Assistant Core has the issue?
core-2022.7.0.dev20220627
What was the last working version of Home Assistant Core?
core-2022.6.0.dev20220506
What type of installation are you running?
Home Assistant Container
Integration causing the issue
ADS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/ads/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
These is just one snippet of the many similar issues reported, figured this stacktrace is sufficient:
ERROR (MainThread) [homeassistant.config] Platform error: light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 618, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 635, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/usr/src/homeassistant/homeassistant/components/ads/__init__.py", line 10, in <module>
import pyads
File "/usr/local/lib/python3.10/site-packages/pyads/__init__.py", line 12, in <module>
from .ads import open_port, close_port, get_local_address, read_state, \
File "/usr/local/lib/python3.10/site-packages/pyads/ads.py", line 18, in <module>
from .pyads_ex import (
File "/usr/local/lib/python3.10/site-packages/pyads/pyads_ex.py", line 82, in <module>
_adsDLL = ctypes.CDLL(adslib)
File "/usr/local/lib/python3.10/ctypes/__init__.py", line 374, in __init__
self._handle = _dlopen(self._name, mode)
OSError: Error loading shared library /usr/local/lib/python3.10/site-packages/pyads/adslib.so: Exec format error
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config.py", line 877, in async_process_component_config
platform = p_integration.get_platform(domain)
File "/usr/src/homeassistant/homeassistant/loader.py", line 627, in get_platform
raise ImportError(
ImportError: Exception importing homeassistant.components.ads.light
### Additional information
_No response_
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:41
Top Results From Across the Web
"exec format error" error running Docker container
I got this error. standard_init_linux.go:190: exec user process caused "exec format error". I want to build pip inside the docker container.
Read more >Docker exec format error - How we sort it out? - Bobcares
The Docker exec format error is a common error, and we fix the docker exec error by adding shebang in the entrypoint of...
Read more >exec format error docker container:linuxserver/transmission
Hello, From what I could gather, the docker container is the only way I can run transmission on QNAP NAS 231p. I followed...
Read more >Docker Engine post-installation steps
This error indicates that the permission settings for the ~/.docker/ directory are incorrect, due to having used the sudo command earlier. To fix...
Read more >Use kaniko to build Docker images - GitLab Documentation
If you receive this error, it might be due to an outside proxy. Setting the http_proxy and https_proxy environment variables can fix the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks for the hints, but this doesn’t worked for me either.
I got the workaround now working with the Add-on: SSH & Web Terminal.
With this Add-on I could connect to HassOS via SSH and use the “docker” workaround described above.
Thanks a lot guys! hopefully this will be fixed soon!
I updates right now to 2022.12.9 and the bug is still there. Only the mentioned workaround above works, but we will see how long.
Maybe somebody with the knowledge about the pylib generation can fix this finally? That would be great!