docker-ipsec-vpn-server VS graylog-docker

IPSEC-L2TP is built into everything. No clients required on Windows, Mac, Android, iOS, Linux, etc. Great Docker container for cutting through most of the difficulty here: https://hub.docker.com/r/hwdsl2/ipsec-vpn-server

e.g: https://mingheng.medium.com/how-to-setup-an-openvpn-server-with-docker-on-an-aws-ec2-in-15-minutes-50443bd31dff atau https://github.com/hwdsl2/docker-ipsec-vpn-server

I'm currently using hwdsl2's VPN Docker container on my server so that I can access my internal network resources while away from my home network. However, it seems that if I connect through my DuckDNS pointer, the connection takes a long time to establish (iOS/macOS will simply say "Connecting..."). I know that this would be a question to raise an issue about, which I did so here. In a nutshell, the developer of the container believes that it would be an issue on DuckDNS' end.

Setup your VPN (one image I found on hub.docker.com is https://hub.docker.com/r/hwdsl2/ipsec-vpn-server)

https://hub.docker.com/r/hwdsl2/ipsec-vpn-server ..?

My suggestion: Don't open up ssh to the world, set up a vpn to your home network instead, then connect to your server just as if it was on the loc network. Here's a possible option to setting up a VPN using docker: https://hub.docker.com/r/hwdsl2/ipsec-vpn-server

I use this and it works very well for me

version: '3' services: # MongoDB: https://hub.docker.com/_/mongo/ mongo: image: mongo:5.0.13 networks: - graylog # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/docker.html elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 environment: - http.host=0.0.0.0 - transport.host=localhost - network.host=0.0.0.0 - "ES_JAVA_OPTS=-Dlog4j2.formatMsgNoLookups=true -Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 deploy: resources: limits: memory: 1g networks: - graylog # Graylog: https://hub.docker.com/r/graylog/graylog/ graylog: image: graylog/graylog:5.0 environment: # CHANGE ME (must be at least 16 characters)! - GRAYLOG_PASSWORD_SECRET=somepasswordpepper # Password: admin - GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918 - GRAYLOG_HTTP_EXTERNAL_URI=http://127.0.0.1:9000/ entrypoint: /usr/bin/tini -- wait-for-it elasticsearch:9200 -- /docker-entrypoint.sh networks: - graylog restart: always depends_on: - mongo - elasticsearch ports: # Graylog web interface and REST API - 9000:9000 # Syslog TCP - 514:514 # Syslog UDP - 514:514/udp # GELF TCP - 12201:12201 # GELF UDP - 12201:12201/udp networks: graylog: driver: bridge

So I surveyed docker images in my personal use:

Postgres (Docker provided - https://hub.docker.com/_/postgres): Debian (with alternates for alpine or other debian versions)

Jellyfin (Developer provided - https://github.com/jellyfin/jellyfin/blob/master/Dockerfile): They use an alpine build step but the final distributed image is debian

Calibre-Web (Linuxserver provided - https://github.com/linuxserver/docker-calibre-web/blob/maste...): Ubuntu

Graylog (Developer provided - https://github.com/Graylog2/graylog-docker/blob/4.2/docker/o...): Debian

Vaultwarden (Developer provided - https://github.com/dani-garcia/vaultwarden/blob/main/docker/...): Debian (with alpine alternate available)

For professional use, our company mandates all images used are built off a common base image, which is Ubuntu based (my previous employer was similar, but used a Red Hat based image).

The ROOT_PASSWORD_SHA2 environment variable is only for the web interface. The underlying container is built on an openjdk Debian Bullseye image, as you can see here: https://github.com/Graylog2/graylog-docker/blob/4.2/docker/enterprise/Dockerfile