For example, today I went to cold crash my beer and tried to use a previous profile that ramped down over three days. I first stopped my 70 F steady control, opened the cold crash profile from my last beer, clicked edit, start now and save. Every time I get “error saving profile.” If I create a new profile and run it it works fine.
You are looking at the docker host and not inside the container, which is why you cannot find /home/brewpi
All directories containing user data that should not be lost when a container is destroyed are mapped to ~/brewpi-data on the host.
The technical details if you want to know them:
The container creation command creates a volume mapping of /data in the container to ~/brewpi-data on the host (~ is /home/pirate on hypriot).
The container startup script creates 4 symlinks, so all brewpi settings and data are stored in this /data directory which lives outside of the container. So you can either access this data on the host in ~/brewpi-data or inside the cointainer (for example through the container console in portainer) in /home/brewpi and /var/www/html
# create symlinks to persisted data outside of container
ln -s -b /data/settings /home/brewpi/settings
ln -s -b /data/data /home/brewpi/data
ln -s -b /data/logs /home/brewpi/logs
ln -s -b /data/html_data /var/www/html/data
On the host, the profiles are stored in /home/pirate/brewpi-data/html_data/profiles.
Thanks - I was able to get into the container and run fix permissions.
If anyone else is reading through this in the future that lacks Linux skills as I do - go into Portainer (Container tab), click brewpi, and then click console (under Container Status). From there you click connect and can copy and paste Elco’s fix permissions command from earlier in the thread.