Error start service with using libseccomp v2.5.1
See original GitHub issueAfter updating libseccomp library from version 2.5.0 to 2.5.1, error starting wsdd service:
wsdd[758]: Traceback (most recent call last):
wsdd[758]: File "/nix/store/qjz0v56g21h9skg678rsdc5wxz31dci2-wsdd-0.6.2/bin/.wsdd-wrapped", line 1684, in <module>
wsdd[758]: sys.exit(main())
wsdd[758]: File "/nix/store/qjz0v56g21h9skg678rsdc5wxz31dci2-wsdd-0.6.2/bin/.wsdd-wrapped", line 1629, in main
wsdd[758]: nm = NetlinkAddressMonitor(s)
wsdd[758]: File "/nix/store/qjz0v56g21h9skg678rsdc5wxz31dci2-wsdd-0.6.2/bin/.wsdd-wrapped", line 957, in __call__
wsdd[758]: obj = super().__call__(*args, **kwargs)
wsdd[758]: File "/nix/store/qjz0v56g21h9skg678rsdc5wxz31dci2-wsdd-0.6.2/bin/.wsdd-wrapped", line 1162, in __init__
wsdd[758]: self.socket = socket.socket(socket.AF_NETLINK, socket.SOCK_RAW,
wsdd[758]: File "/nix/store/jdp800qwb3v330ggl6iq722ww96q2444-python3-3.8.6/lib/python3.8/socket.py", line 231, in __init__
wsdd[758]: _socket.socket.__init__(self, family, type, proto, fileno)
wsdd[758]: OSError: [Errno 97] Address family not supported by protocol
systemd[1]: samba-wsdd.service: Main process exited, code=exited, status=1/FAILURE
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
issue creating containers due to seccomp failure ( error ...
This looks like a docker issue due to using an out of date version ... ERROR: for webpack Cannot start service webpack: OCI...
Read more >1908281 – libseccomp: Add support for newer system calls ...
1-3.el7.x86_64 container-selinux-2.119.2-1.911c772.el7_8.noarch This version has faccessat2 support on the Docker CE side. Then run: docker run fedora:rawhide / ...
Read more >3 Common Tasks — The Yocto Project ® 4.1.999 documentation
During the build process, BitBake displays an error on starting if it detects ... a service, which is a process that usually starts...
Read more >Docker Compose release notes | Docker Documentation
Fixed issue of compose down command that when executed in contexts without any services started or resources to be deleted was returning an...
Read more >dial tcp: lookup docker on x.x.x.x:53: no such host error runner ...
When running gitlab-runner inside docker on an armhf platform the following error is thrown when trying to run docker login:.
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 FreeTop 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
Top GitHub Comments
Great.
No. These aren’t address families.
Created a PR to fix the WSDD service in NixOS - https://github.com/NixOS/nixpkgs/pull/107112