-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't install docker? #19
Comments
Not sure what the problem is there. iptables 1.8.7 is a current version. Maybe some kernel module is missing? If you figure it out, I'd gladly accept a PR. |
The tools shell with check-config.sh is available here
|
PR #20 Introduces kernel features that enabled using docker / podman along with a few other changes. |
@codekow @Heisath Problem is with missing IP Table Modules again
|
Podman and Docker both have the same issue |
What kernel module is missing?
…On Sun, Jan 28, 2024, 2:31 AM Mruru ***@***.***> wrote:
docker.service: Start request repeated too quickly.
Podman and Docker both have the same issue
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMDIWEFBRVF6KN2JRXQDA3TYQYEFBAVCNFSM6AAAAAAXZN24YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGUYTKMBWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Verify which kernel config you are using.
`config/linux-default.config` should be copied over the other version
config and updated. A PR could be created for 6.x.
I only updated the default and ver 5.15 kernel config. I did not update any
others.
…On Sun, Feb 4, 2024, 10:54 AM Cory Latschkowski ***@***.***> wrote:
What kernel module is missing?
On Sun, Jan 28, 2024, 2:31 AM Mruru ***@***.***> wrote:
> docker.service: Start request repeated too quickly.
>
> Podman and Docker both have the same issue
>
> —
> Reply to this email directly, view it on GitHub
> <#19 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AMDIWEFBRVF6KN2JRXQDA3TYQYEFBAVCNFSM6AAAAAAXZN24YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGUYTKMBWHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Same problem here,
It boots, OMV workbench starts, but while trying to log in it shows error "Failed to connect to socket: No such file or directory", and podman/docker still doesnt launch properly. Tested on debian 12 bookworm, kernel 6.1.78 LTS. |
Issues above should be addressed in #24 - updated 6.1 kernel config Tested on kernel 6.1.87 and debian 12 (bookworm) |
Using this script i modified linux-6.1.y.config and managed to build kernel and modules so that docker/podman works perfectly fine. |
Here is a modified config for 6.1.104 in case someone need, I'd love to submit a PR if needed |
when i try to run
error msg like this:
Mycloud:/var/lib/dpkg# dockerd
INFO[2023-05-08T06:48:44.599345520+02:00] Starting up
ERRO[2023-05-08T06:48:44.647317040+02:00] failed to mount overlay: no such device storage-driver=overlay2
ERRO[2023-05-08T06:48:44.647880760+02:00] exec: "fuse-overlayfs": executable file not found in $PATH storage-driver=fuse-overlayfs
INFO[2023-05-08T06:48:44.664998520+02:00] Loading containers: start.
INFO[2023-05-08T06:48:44.695349640+02:00] unable to detect if iptables supports xlock: 'iptables --wait -L -n':
iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument
error="exit status 4"INFO[2023-05-08T06:48:45.072778360+02:00] stopping event stream following graceful shutdown error="" module=libcontainerd namespace=moby
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument
(exit status 4)
The text was updated successfully, but these errors were encountered: