Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    If you want answers here, you should migrate your question here — copy it here entirely, and delete the ServerFault question. Otherwise one or both will be closed (questions aren’t supposed to be posted on multiple SE sites). Would you care to explain why /etc wouldn’t be available in containers? Are you aware of the /etc description in the FHS? If configuration shouldn’t go in /etc, where would you consider it appropriate to place it? Commented Jun 11, 2024 at 21:04
  • This is one of those questions that straddles the line between administration (hence ServerFault) and programming. That being the case, I thought this group might have an interest as well. When in Rome. Commented Jun 11, 2024 at 21:32
  • 1
    The question of where apps' local environments should be set has been answered in different ways over time. The old school answer is /usr/local/. More recent practice is to use /opt/<company>. The /etc directory is so tightly tied to the OS it seems like a bad idea to use it for this kind of localization. Commented Jun 11, 2024 at 21:34
  • Finally, to your point about the link, I would say that proves my point -- everything there is for the OS, not the applications. In my understanding of Containers, the OS is inaccessible from the application, and in my old school view, /etc/ is part of the OS. Honestly, this is moot -- my employer was doing this long before I arrived, and they are unlikely to change. Just wanted to see what others did. Commented Jun 11, 2024 at 21:41