Hmm, I thought the install script was properly doing that but it might not be. I’ll double-check. But ultimately yes, you do need a
$PANDIR/.env file that contains some of the variables.
I usually don’t use the
-d option and it keeps everything in the foreground. That will show some error messages from startup in a clean fashion. You would then need to open another terminal to do anything. It’s mostly personal preference for how you would want set up.
Docker works like a virtual machine, so all of the required software and files are loaded inside the docker image. When you run a copy of the docker image it is referred to as a docker container. In this way you can have many instances (i.e. docker containers) of the same virtual machine-like setup (i.e. the docker image).
So here what you are seeing are errors that are happening inside the virtual container. This container contains its own small version of linux and filesystem, so the
/opt errors you are seeing are from inside the container. If using the docker setup you shouldn’t need to install any additional software such as anaconda.
Does the main computer have a
panoptes user? The best would be to grant the
panoptes user as the owner and group of
$ sudo chown -R panoptes:panoptes $PANDIR
There might be some misplaced owner/permissions from a previous setup so the above command should fix all of that.
The errors with connecting to the arduino might just be port issues (as listed in the config file). I think @tmcook had made some notes in the document about trying to determine the usb ports. It mostly has to do with the order in which they were plugged in but sometimes takes a bit of troubleshooting.
See if any of the above helps with the permission issues and then maybe try to unplug the usb ports and only plug in one at a time to test and verify things. i.e. just plug in the weather station, figure out what port it is, try to load it via peas_shell, etc.