Images are a year out of date

[aaronmgriffin]

Describe the issue

Images on both dockerhub and github packages are very outdated, and the repo is behind the parent wireguard repo. Please update!

Expected behavior

The readme suggests weekly/monthly image updates on :edge and :latest tags

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[KaKi87]

Bump

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[KaKi87]

Up

[jaycuse]

Created a PR to update base image. Hopefully this can get us a new build.
#178

I see that part of the reason there are no new builds is because the ci is failing since old base image is no longer around:
https://github.com/bubuntux/nordlynx/actions/runs/11730626877/job/32678909039

[jaycuse]

Unfortunately the build is still failing.

Error: buildx failed with: ERROR: failed to solve: ghcr.io/linuxserver/baseimage-alpine:3.20: failed to resolve source metadata for ghcr.io/linuxserver/baseimage-alpine:3.20: no match for platform in manifest: not found

It appears to be missing some target platforms.

[arkandias]

I decided to update this image to catch up with the upstream linuxserver/wireguard repo a few weeks back, as it seemed that it was not maintained anymore. Since then PR #178 has been merged, but I'm sharing my work for those interested: arkandias/docker-nordlynx.
It will be kept synchronized with linuxserver/wireguard image.

As I was trying to understand and streamline the configuration, I eventually rewrote most of the code but the workflow remains globally the same. Key differences include:

• Migrated to s6-overlay v3 to align with linuxserver/wireguard (this is the most visible modification as it completely change the subdirectory structure of the project).
• Support connection using access token (as it is now possible to retrieve the private key using NordVPN API).
• IPv6 disable (as I lack knowledge on this matter and did not want to use code I don't understand).

Any feedbacks or contributions are very much welcome!

[KaKi87]

Hi,
Thank you !
How do I make requests through it ?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[KaKi87]

@arkandias 🙏