mirror of
https://github.com/hwdsl2/docker-ipsec-vpn-server.git
synced 2026-04-26 01:55:53 +03:00
[GH-ISSUE #83] Cannot modprobe af_key #71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @imajou on GitHub (Jul 18, 2018).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/83
Good afternoon.
Using this VPN image with Docker 18.03 on CoreOS 1745
Got this error when launching:
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.48-coreos-r2/modules.dep.bin' modprobe: FATAL: Module af_key not found in directory /lib/modules/4.14.48-coreos-r2 Redirecting to: /etc/init.d/ipsec startThat is running configuration:
docker run \ --name ipsec-vpn-server \ --env-file ./vpn.env \ --restart=unless-stopped \ -p 500:500/udp \ -p 4500:4500/udp \ -v /lib/modules:/lib/modules:ro \ -d --privileged \ hwdsl2/ipsec-vpn-serverI suppose, I should somehow modify the volume exposing with
-v /lib/modules:/lib/modules:roAny obvious modification of exposure does not work.
@hwdsl2 commented on GitHub (Aug 27, 2018):
@Imajou Hello! CoreOS is not currently supported.
@hwdsl2 commented on GitHub (Sep 12, 2018):
@Imajou Hello! I tried to reproduce this issue under CoreOS 1855.4.0 but the
sudo modprobe af_keycommand runs fine both outside and inside the Docker container.I think there is a problem with your system's kernel modules, perhaps your kernel module folder name in
/lib/modulesdoes not match the version of your kernel (checkuname -r)?The latest version of this Docker image is now compatible with CoreOS, with the fix in commit
0d09e01.@sudanking commented on GitHub (Jun 27, 2019):
I still can not run Docker image in CoreOS even after I remove aes256-sha2_512 ..... any suggestions??
error:
initial Main Mode message received on 172.17.0.2:500 but no connection has been authorized with policy PSK+IKEV1_ALLOW
@hwdsl2 commented on GitHub (Jul 10, 2019):
@sudanking The error probably means you are mixing IPsec/L2TP clients with IPsec/XAuth clients and connecting them shortly after one another. Try restarting the Docker container.
If still not working, backup your VPN credentials, get the latest version of the Docker image, then re-create your Docker container and try again.