settings not sicking

Shawn H

September 23, 2020 14:17

So changes I make as well as installed stuff does not stick after a reboot.

I added samba and sleeptest cli and after a reboot it is all gone...

Anyway to no have it wipe everything?

I am on 1.971 alpha and thought that was going to help but nope...

Comments

6 comments

FF

September 23, 2020 15:12
I haven't tested yet but ~/pi should persist and you can add scripts loaded at boot time under:
```
/home/pi/.firewalla/config/post_main.d
```
https://help.firewalla.com/hc/en-us/community/posts/360050025114/comments/360012910734#community_comment_360012910734
0

Comment actions Permalink
Shawn H

September 23, 2020 15:48
2 things though.

1. There is no post_main.d dir.

2. doesn't help with it wiping samba and speedtest installed via apt.
0

Comment actions Permalink
Firewalla

September 23, 2020 16:19
You can make that directory if it is not there. And you need to be on early release https://help.firewalla.com/hc/en-us/articles/360052804993

If you have binaries, we recommend to install them in ~pi, the content there will persist. As of apt ... at the moment, no, we try to discourage using that. But if you know how to do bash, you can easily script something and have apt installed via the post_main.d every time.

Also a quick reminder, the post_main.d is called when ever the box starts, or the firewalla stack get reloaded. So please do assume there is a chance what ever you are doing likely already loaded, so please do the proper clean up. (We will provide better guides and also documentation soon).
0

Comment actions Permalink
Shawn H

September 23, 2020 16:34
Thanks much, you guys rock!
0

Comment actions Permalink
FF

September 23, 2020 17:31
@Firewalla,
is it fair to say that the best approach would be to add whatever extra are required inside dockers which get loaded at boot time from the post_main.d/ ?
0

Comment actions Permalink
Firewalla

September 23, 2020 18:14
@FF

We try to encourage people to install stuff in dockers, since it is the most clean way to do things. But, if there are thing that can not be docker (things requires direct network access ... for example tshark), it may make sense just dynamically install these things in that script. (using apt-get ... )
0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?