Docker containers are running with "root" user by default, which may not be the best choice if we don't need root privileges. It may cause security issues down the road. Also, the owner of the container outputs would be the "root" user, which makes it harder for a non-root user on the host to work with them. So, we currently use a non-root user, "user" with "UID 5000", as the user to run the containers. This user is most probably not available on the host. So, the owner of the files and folders created by the containers are shown as "5000". On the other hand, the flare-host/shareddirectory which is created by the flare-install.sh script belongs to the user on the host who has installed FLARE containers for the first time, probably "ubuntu" user. These different users may be a source of complication if we are not careful about the ownership and permission of the files and folders.
Docker containers are running with "root" user by default, which may not be the best choice if we don't need root privileges. It may cause security issues down the road. Also, the owner of the container outputs would be the "root" user, which makes it harder for a non-root user on the host to work with them. So, we currently use a non-root user, "user" with "UID 5000", as the user to run the containers. This user is most probably not available on the host. So, the owner of the files and folders created by the containers are shown as "5000". On the other hand, the
flare-host/shareddirectory which is created by theflare-install.shscript belongs to the user on the host who has installed FLARE containers for the first time, probably "ubuntu" user. These different users may be a source of complication if we are not careful about the ownership and permission of the files and folders.