/entrypoint.sh: 34: exec: 1000:1000: not found

[drees-clark]

Had Flatnotes running perfectly in Docker on Synology NAS.
Possibly after this latest update the container stops with above error.

EDIT:
Image used: dullage/Flatnotes:latest
I tried different users in PUID and PGID, from root to admin to normal user account.

[Code-Otto]

Oh whoops, this is related to my merged changes here:
43b2ee0#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2L34-R34

This PR added a new experimental Alpine Linux-based Dockerfile which results in a much smaller Flatnotes container image.
Since the gosu tool used at the entrypoint is not available at Alpine Linux we used the equivalent su-exec instead. To keep the same entrypoint script compatible with both images I added a EXEC_TOOL variable to the Dockerfile telling the command of the tool (either EXEC_TOOL=gosu or EXEC_TOOL=su-exec)

However looks like when updating the Docker container this environment variable doesn't gets defined and is causing the script to fail

A fix for this would be adding the following to the /entrypoint.sh script to keep it working for existing users:

if [ ! "$EXEC_TOOL" ]; then
    EXEC_TOOL=gosu
fi

As a hotfix while the fix is ready you can try manually adding the above to the beginning of this script inside the container, or just reinstalling Flatnotes

[drees-clark]

Thank you for the clarification and explanation. Unfortunately, I'm unable to find the entrypoint.sh file.
Can you give me pointers as to where the file might be in a Docker environment on Synology NAS?

EDIT:
Nevermind, I replicated the stack, and miraculously it works again now.

[drees-clark]

See comment by Code-Otto

[banjuer]

Oh whoops, this is related to my merged changes here: 43b2ee0#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2L34-R34

This PR added a new experimental Alpine Linux-based Dockerfile which results in a much smaller Flatnotes container image. Since the gosu tool used at the entrypoint is not available at Alpine Linux we used the equivalent su-exec instead. To keep the same entrypoint script compatible with both images I added a EXEC_TOOL variable to the Dockerfile telling the command of the tool (either EXEC_TOOL=gosu or EXEC_TOOL=su-exec)

However looks like when updating the Docker container this environment variable doesn't gets defined and is causing the script to fail

A fix for this would be adding the following to the /entrypoint.sh script to keep it working for existing users:

if [ ! "$EXEC_TOOL" ]; then
    EXEC_TOOL=gosu
fi

As a hotfix while the fix is ready you can try manually adding the above to the beginning of this script inside the container, or just reinstalling Flatnotes

wil it merged into next release? unfortunately, i met the same issue and i don't no how to edit this code in docker...

[Code-Otto]

I've opened a pull request with a proposed fix
Since I'm not a maintainer I cannot do the changes directly however expect that when @dullage is back an updated image with the fix will be available soon

[dullage]

Fix is now available in v4.0.4. Thanks @Code-Otto.

[dullage]

@banjuer - Were you also running flatnotes on a Synology?

[banjuer]

@banjuer - Were you also running flatnotes on a Synology?

yes and now it worked well in v4.0.4, Thank you all !