Skip to content

Conversation

@felbinger
Copy link

Using fully qualified domain names as unique identifier for containers improves identification of containers on large (potentially multi tenant) hypervisors.

In the current version using a container name containing a dot doesn't work. I forked microvm.nix and adjusted it so that fqdn's are used by default.

Should we try to upstream this? If yes how?

I drafted this change because merging this would result in breaking changes if networking.domain is being set for a machine.

Copy link
Member

@SuperSandro2000 SuperSandro2000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modules that accept a mere networking.hostName but prefer a fully qualified domain name may use networking.fqdnOrHostName instead.

https://search.nixos.org/options?channel=unstable&show=networking.fqdn&query=networking.fqdn

@felbinger
Copy link
Author

I haven't had the time to test yet, will do in the next days...

@felbinger
Copy link
Author

I haven't had the time to test yet, will do in the next days...

Ok works. Now this change works without breaking changes if networking.domain is NOT set.

If I am correct, systems that have a domain set will still encounter breaking changes, right?

How should we proceed?

@felbinger felbinger marked this pull request as ready for review October 21, 2025 16:07
@felbinger felbinger changed the title chore: replace hostName with fqdn chore: replace hostName with fqdnOrHostName Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants