Is your feature request related to a problem? Please describe.
I am aware that no PRs are desired for new Docker Base Images. Due to a bug I'm still contacting you, maybe this could be the start of the update of the Alpine Base Image (3.10 -> 3.11).
According to the github, Alpine 3.10 is still used for acme and dockerapi. The current images on dockerhub are 3.11. I guess there was a local cache problem again.
# docker exec -it mailcowdockerized_acme-mailcow_1 sh -c "cat /etc/alpine-release"
3.11.6
# docker exec -it mailcowdockerized_dockerapi-mailcow_1 sh -c "cat /etc/alpine-release"
3.11.6
# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
mailcow/acme 1.70 94144a1d2625 2 days ago 112MB
mailcow/dockerapi 1.36 0baf86154dcc 2 days ago 73.9MB
If there is already Alpine 3.11 in the world due to a bug, we can update the images to Alpine 3.11 officially.
Describe the solution you'd like
New Dockerhub images, maybe update to Alpine 3.11
Additional context
Avoiding the local cache problem
General overview of the used Base Images.
Info: The owner of ipv6nat unfortunately refuses to make an update.
Is your feature request related to a problem? Please describe. I am aware that no PRs are desired for new Docker Base Images. Due to a bug I'm still contacting you, maybe this could be the start of the update of the Alpine Base Image (3.10 -> 3.11).
According to the github, Alpine 3.10 is still used for acme and dockerapi. The current images on dockerhub are 3.11. I guess there was a local cache problem again.
If there is already Alpine 3.11 in the world due to a bug, we can update the images to Alpine 3.11 officially.
Describe the solution you'd like New Dockerhub images, maybe update to Alpine 3.11
Additional context Avoiding the local cache problem
General overview of the used Base Images. Info: The owner of ipv6nat unfortunately refuses to make an update.