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
By overriding the entrypoint to get into the container's shell, I issued ccm-service start with the same result, and found this in /var/log/nginx/error.log:
2022/09/09 19:00:13 [emerg] 332#332: socket() [::]:80 failed (97: Address family not supported by protocol)
Possibly relevant: the host is IP4-only. Is that an exotic scenario? Many desktop linux users disable IP6.
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
Expected:
... and a running container.
Actual:
... and the container exits.
By overriding the entrypoint to get into the container's shell, I issued
ccm-service start
with the same result, and found this in/var/log/nginx/error.log
:Possibly relevant: the host is IP4-only. Is that an exotic scenario? Many desktop linux users disable IP6.
The text was updated successfully, but these errors were encountered: