I must be missing a fundamental concept here, but when I browse files in HASSIO Configurator, I don’t see the same files as when I SSH to my Rasberry PI (using root with keys if that matters)
With HASS Configurator, if I edit /config/configuration.yaml , then I do see the changes when SSHing into the box.
But if I look at /etc or /etc/ssh/sshd_config for example, they’re not the same files. If I create a folder in /etc , it doesn’t show up. Basically, I can create a “test” folder in /etc in both configurator and by SSHing into the box, and there’s no collision.
The concept of docker. Each “application” is it’s own container. /etc in one is not /etc in another. You can’t just edit files like that in different containers. They will be wiped out on next update anyway.
To put it simply, you don’t edit files outside the directories that are shared.
Thanks for the feedback. So, if I read the homepage of the Configurator addon, or if I look at my Configurator addon config, where does it say that it deals with /config only ?
When you are inside the configurator, you’re essentially inside another computer in the network. Not really but it’s the best way to describe it. When you’re in the SSH add-on, you’re inside ANOTHER computer on your network, and when in the home assistant container, you’re in yet ANOTHER.
Each container running has it’s own “filesystem”. It is it’s own entity. So if you edit /etc in the configurator you are editing the files inside that container only. When you SSH in, you’re in a different container that has it’s own /etc. They aren’t linked.
The configurator is not only a hassio addon. There’s a standalone version as well, which can be used to modify files on the regular filesystem. With hassio this doen’t really make any difference. But on a standalone install where people want to prohibit modification of other files it’s used to deny access to those external files. So you can just ignore this option.