Latest fails to start /usr/local/bin/init.sh not found

[adefaria]

Recently, arch-delugevpn was updated, and now it fails to start, stating /usr/local/bin/init.sh not found. I'm on Synology and the latest (2.2.0-1-04). I had to downgrade to 2.2.0-1-03.

[curtbraz]

Also seeing this same behavior. Always just update to the latest tag, but this is the first time it broke with the same error. Also on Synology (DSM 7.2.2-72806 Update 4)

[martach]

I had the same problem on Synology. My old container was created by Container manager. The problem disappeared when I created a new container using a yaml file through the Projects tab. In the yaml file I added the configuration from my old container - good as new!

The problem is possibly related to "Executive command /bin/bash /usr/local/bin/init.sh" in my old container, whereas the Dockerfile now says

# run script to set uid, gid and permissions
CMD ["/bin/bash", "init.sh"]

[Devo-McDuff]

I'm also having the same issue on DSM 7.2.1-69057 Update 8 since updating to the latest release.

@martach Would you be able to provide some advice on how you created the yaml file to use as a project as a workaround? I exported my current container config as a json and tried an online convertor to yaml, but the import flagged loads of errors with that file. Did you try something like this https://github.com/Red5d/docker-autocompose ?

Thanks

[monboulou]

Same issue here
I am interested in a workaround

[Devo-McDuff]

Same issue here I am interested in a workaround

I had no luck. For now, I removed the container and added the version before it broke, rather than latest tag

[xboxhacks]

I'm also getting this error after updating the container on my synology nas.

[pbojanczyk]

Looks like it was done intentionally in this commit:
1b6d03d

[alexk403]

If anyone is still running into this issue, I was able to fix it through the Synology Container Manager like this:

1. Go to old container and duplicate it
2. Change the PATH environment variable to be: /usr/local/bin/system/scripts/docker:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
3. Change the execution command to be: /bin/bash init.sh

Everything now works. I was able to figure this out by temporarily creating a new container with the updated image to see what default settings it had changed.

[jfdhuiz]

the arch-qbittorrentvpn repo has a similar ticket, and I figured a similar possible as solution as @alexk403 but via docker-compose.yml also I only had to change the PATH, not changed the command binhex/arch-qbittorrentvpn#353 (comment)