Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/etc/docker/daemon.json is now named /etc/docker/key.json #10138

Closed
khennicb opened this issue Jan 13, 2020 · 6 comments
Closed

/etc/docker/daemon.json is now named /etc/docker/key.json #10138

khennicb opened this issue Jan 13, 2020 · 6 comments

Comments

@khennicb
Copy link

File: config/daemon/ipv6.md

Current sentence :
Edit /etc/docker/daemon.json and set the ipv6 key to true

Should be :
Edit /etc/docker/key.json and set the ipv6 key to true

@jangrewe
Copy link

@khennicb No, it should not. Those are completely different files with completely different purposes. Please remove/update your comment before somebody catches a footbullet.

@khennicb
Copy link
Author

It's not that I don't trust your words @jangrewe
But do you know where I can read about the purpose of each of those two files ?

@jangrewe
Copy link

jangrewe commented Feb 12, 2021

Well, it's kinda obvious from the filename that one is for the configuration for the daemon, and the other contains a key.
There's no official documentation about it, AFAIK, but that's also because it's a file that nobody should ever need to touch, if he doesn't know that he's doing - or in other words: the exact opposite of a config file.

Here's some background info, though: moby/moby#7667

How did you even come to the conclusion that this is now the new name of the file? Just because it exists and contains some JSON? I think the Docker docs mention everywhere that you have to create the file yourself, if it doesn't exist yet.

@khennicb
Copy link
Author

Alright, I see

How did you even come to the conclusion that this is now the new name of the file? Just because it exists and contains some JSON? I think the Docker docs mention everywhere that you have to create the file yourself, if it doesn't exist yet.

Yea, most likely.
It was a year ago, I don't remember

@khennicb
Copy link
Author

thanks for replying to my old issue :)

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker docker locked and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants