You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i struggle since 2 days with the message ckan-1 | socket(): Address family not supported by protocol [core/socket.c line 82]
which immediatly crashes my container.
I rebuilt the image just 2 days ago and now the same image tag does not work anymore.
My Dockerfile uses ckan/ckan-base:2.10.4.
Why did the Docker Image change?
It seems the container image versioning does not follow semver of ckan.
What is the best practice to guarantee nothing is breaking when using the ckan container?
On my local machine everything runs fine.
The production machine i use, the hoster has disabled ipv6 due to compliance bingo.
I saw you merged #67 two weeks ago, binding to the local ipv6 device by default.
My assumption is this is causing my issue.
In general i'd favor to support ipv6 as well, but ipv6 is often not an option.
Especially in security enhanced networks it is usual to disable ipv6 by default to reduce complexity and attack vectors.
To solve this i propose an environment variable to define the network interface to bind to, binding to ipv6 localhost [::] by default, but allowing to override it.
What do you think?
The text was updated successfully, but these errors were encountered:
As workaround i replace the ipv6 [::] address with the ipv4 0.0.0.0 address when building my custom Dockerfile using
RUN sed -i 's#\[::\]#0.0.0.0#' start_ckan.sh
But for standalone hosting, that does not use a custom Dockerfile this approach is not applicable.
It may be worth to introduce a configuration option.
Hi @amercader ,
i struggle since 2 days with the message
ckan-1 | socket(): Address family not supported by protocol [core/socket.c line 82]
which immediatly crashes my container.
I rebuilt the image just 2 days ago and now the same image tag does not work anymore.
My Dockerfile uses
ckan/ckan-base:2.10.4
.Why did the Docker Image change?
It seems the container image versioning does not follow semver of ckan.
What is the best practice to guarantee nothing is breaking when using the ckan container?
On my local machine everything runs fine.
The production machine i use, the hoster has disabled ipv6 due to compliance bingo.
I saw you merged #67 two weeks ago, binding to the local ipv6 device by default.
My assumption is this is causing my issue.
In general i'd favor to support ipv6 as well, but ipv6 is often not an option.
Especially in security enhanced networks it is usual to disable ipv6 by default to reduce complexity and attack vectors.
To solve this i propose an environment variable to define the network interface to bind to, binding to ipv6 localhost
[::]
by default, but allowing to override it.What do you think?
The text was updated successfully, but these errors were encountered: