Do you know of a way to change this UID:GID of the user that runs insync?

I have tried changing the user when starting the docker using the -u flag, however it fails to start because of permission errors when trying to create the docker. It appears to be unable to copy over the install folder scripts.
I have also tried cloning your repository and modifying the dockerfile to have a USER block at the very end, after it copies files. However insync is unable to start.
I have kind of started trying to tweak the script files to see if I can get insync to run as a different user, but haven't had much luck yet.
I am not familiar with the s6 overlay that appears to be what is scheduling when to run insync.
Figured before I wasted more hours on it I would ask in case you know the answer already.

The reason I am trying to accomplish this is so my Google Drive files are not owned by root:root, as they are now.
I know I could create a script on the local machine to run every so often and change owners, but I figured if I could just change what uid:gid the docker is using for insync this would solve it at the source.
Any help you have would be greatly appreciated.

New Issue since it is a new topic hope that's ok.
I did have this issue before you switched the user account info so this might not be related to making that change.
Whenever I try to run manage_sync I get this error:
"Invalid number of arguments for manage_selective_sync
insync-headless manage_selective_sync EMAIL
Manage selective sync settings of account through a curses interface"

So thinking I needed to specify the email address after.
So I tried manage_sync [email protected]
and I get the same error.

It looks like the script is calling a username variable that is no longer used with the multi user.
So not sure if you have a good idea on how to do the multiuser

I have a couple of thoughts
1.) enter: manage_sync {1,2,3} - They would enter either 1-3 and then the script would look at the number entered and run the command pulling in that username variable.
2.) enter manage_sync - it will then list the Username variable values and then they would select 1,2,3 and then it would continue. This could be combined with above, they could enter what number they want when running, if they dont enter a number then it would present them with the list.
3.) enter manage_sync EMAIL - They enter the email address they want to modify
This one could simply be to update the command to:
TERM=xterm sudo -u insync exec /usr/bin/insync-headless manage_selective_sync $1

Not sure if you think one is easier than the other for the user, but as it stands these scripts(ignore & sync) dont work
Also when updating the scripts need to switch to the insync user when running the command
I believe I could write up the script combining option 1 & 2 above, I believe I already listed how to make opt 3 work.
Just let me know.
Thanks

Hi

I have RPI 3 with OMV 5. I just deployed your container using portainer. I have followed your instructions. Container is running but when I try to run commands I have the below error:

In the logs I have below:

standard_init_linux.go:211: exec user process caused "exec format error"

My settings:

Any ideas or suggestions what went wrong?

Thansk

Tom

I have been wondering if adding support for ARM architectures would be possible (mostly for raspberry pi)

Unfortunately there's no separate insync package in raspbian.
I found this: https://help.insynchq.com/en/articles/112904-linux-insync-on-raspberry-pi

armhf and armel arhives are provided.

Obtaining the following error when trying to setup InSync in docker. Presumably, something changed on Google's end.
"Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In."

Summary

https://insynchq.com/auth leads me to a google page that states "Access blocked: Insync’s request is invalid". This is the exact URL that is returned:

https://accounts.google.com/signin/oauth/error/v2?authError=ChVyZWRpcmVjdF91cmlfbWlzbWF0Y2gSlgJUaGUgcmVkaXJlY3QgVVJJIGluIHRoZSByZXF1ZXN0LCB1cm46aWV0Zjp3ZzpvYXV0aDoyLjA6b29iLCBjYW4gb25seSBiZSB1c2VkIGJ5IGEgQ2xpZW50IElEIGZvciBuYXRpdmUgYXBwbGljYXRpb24uIEl0IGlzIG5vdCBhbGxvd2VkIGZvciB0aGUgV0VCIGNsaWVudCB0eXBlLiBZb3UgY2FuIGNyZWF0ZSBhIENsaWVudCBJRCBmb3IgbmF0aXZlIGFwcGxpY2F0aW9uIGF0IGh0dHBzOi8vY29uc29sZS5kZXZlbG9wZXJzLmdvb2dsZS5jb20vYXBpcy9jcmVkZW50aWFscy9vYXV0aGNsaWVudBpVaHR0cHM6Ly9kZXZlbG9wZXJzLmdvb2dsZS5jb20vaWRlbnRpdHkvcHJvdG9jb2xzL29hdXRoMi9vcGVuaWQtY29ubmVjdCNzZXRyZWRpcmVjdHVyaSCQAzLyAggBEpYCVGhlIHJlZGlyZWN0IFVSSSBpbiB0aGUgcmVxdWVzdCwgdXJuOmlldGY6d2c6b2F1dGg6Mi4wOm9vYiwgY2FuIG9ubHkgYmUgdXNlZCBieSBhIENsaWVudCBJRCBmb3IgbmF0aXZlIGFwcGxpY2F0aW9uLiBJdCBpcyBub3QgYWxsb3dlZCBmb3IgdGhlIFdFQiBjbGllbnQgdHlwZS4gWW91IGNhbiBjcmVhdGUgYSBDbGllbnQgSUQgZm9yIG5hdGl2ZSBhcHBsaWNhdGlvbiBhdCBodHRwczovL2NvbnNvbGUuZGV2ZWxvcGVycy5nb29nbGUuY29tL2FwaXMvY3JlZGVudGlhbHMvb2F1dGhjbGllbnQaVWh0dHBzOi8vZGV2ZWxvcGVycy5nb29nbGUuY29tL2lkZW50aXR5L3Byb3RvY29scy9vYXV0aDIvb3BlbmlkLWNvbm5lY3Qjc2V0cmVkaXJlY3R1cmk%3D&client_id=468017360789-e4camv9a5n4e90tk4vrpk49qonmcm95s.apps.googleusercontent.com

The OneDrive link works fine. It's just strange because I thought someone else would've reported this by now. I thought it had something to do with my computer/account, but this same message will display from anywhere.

Hi,

how do i pass the environment variables to change the UID and GID from 12345 to 1000 ?

There are two environment varialbes for the base image which should allow to change the UID and GID in /etc/passwd and /etc/group... However, i am passing both variable for user insync and group insync but it does not change the UID or GID in the image.

Would be great if i can get some help. Other then this issue the sync seems to work fine.

Here is my docker-compose configuration :

insync-app:
image: tiredofit/insync
container_name: insync-app
networks:
- vlan99
environment:
- ZABBIX_HOSTNAME=insync-app
- INSYNC1_USERNAME=xxxx
- INSYNC1_AUTH_CODE=xxxx
- INSYNC_DOWNLOAD=ms-office
- DEBUG_PERMISSIONS=TRUE
- USER_INSYNC=1000
- GROUP_INSYNC=1000
- TIMEZONE=${TZ}

volumes:
  - ${DOCKERDIR}/insync:/data
restart: always

thx!

Is there a switch to insync_headless 3.x in the works? certain licenses don't work anymore with the 1.5 version..

this line in 10-insync causes cron to start, even if ENABLE_CRON=FALSE

and then this line in services/04-cron/run adds another logrotate command to the root crontab.

is there any reason to add insync-headless to the crontab?
that instance won't be managed by s6