Disable IPv6

Open
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker, shell
Domain
networking

Research direction

Start by examining the container's environment options and chrony configuration entry points for how IPv6 sockets are enabled. Use the reported [::1]:323 and [::]:123 log messages as the reproduction signal; done means documenting or providing a supported way to disable IPv6 without those socket errors.

Written by the indexing model from the issue text.

Description

Hello,

Is there an environment option to disable IPv6?
I see this in the logging :

[Chrony] 2026-04-28T07:19:10.777309612Z 2026-04-28T07:19:10Z Disabled control of system clock
[Chrony] 2026-04-28T07:19:10.789473156Z 2026-04-28T07:19:10Z Could not open command socket on [::1]:323
[Chrony] 2026-04-28T07:19:10.794215325Z 2026-04-28T07:19:10Z Could not open NTP socket on [::]:123

I have disable IPv6 on my Pi.

Dominant language
Shell
Stars
119
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dockur/chrony

All issues in dockur/chrony

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.