Hello,
First post here so want to start with a huge thank you to all the work done here! Love using libvips.
Apologies but I'm new to compiling binaries, so suspect I'm doing something wrong.
On Win11 and VS Code, when running the build.sh script, the script runs through, I can see the binaries in the snapshot folder in docker container. But right at the end, I always receive the error '/bin/bash: package.sh: No such file or directory'.
I've managed to recover all the binaries from the snapshot, and they appear to be working.
I've asked 'Gordon' in Docker desktop to analyse the issue and below is the response.
**The package.sh file exists. The issue is that the ENTRYPOINT runs before the COPY . /data completes in the Docker build context. The problem is likely that package.sh is not executable or the file isn't being copied correctly. Let me check the script:
Fixed. The issue was that your ENTRYPOINT referenced package.sh without an absolute path. When bash runs with that ENTRYPOINT, it's in /data/packaging but package.sh wasn't in the shell's PATH. I changed it to use the full path /data/packaging/package.sh and added a chmod +x to ensure it's executable. Rebuild your image and the container should find the script now.**
After the fixed was applied by Gordon, I had different errors at the end of compiling.
I suspect I have an issue with my setup, where the working directory is not being set correctly in the shell.
End of docker file below that's not working for me.
**# The packaging dir is mounted here
WORKDIR /data/packaging
ENTRYPOINT ["/bin/bash", "package.sh"]**
Can you please advise?
Many thanks
Steve
Hello,
First post here so want to start with a huge thank you to all the work done here! Love using libvips.
Apologies but I'm new to compiling binaries, so suspect I'm doing something wrong.
On Win11 and VS Code, when running the build.sh script, the script runs through, I can see the binaries in the snapshot folder in docker container. But right at the end, I always receive the error '/bin/bash: package.sh: No such file or directory'.
I've managed to recover all the binaries from the snapshot, and they appear to be working.
I've asked 'Gordon' in Docker desktop to analyse the issue and below is the response.
**The package.sh file exists. The issue is that the ENTRYPOINT runs before the COPY . /data completes in the Docker build context. The problem is likely that package.sh is not executable or the file isn't being copied correctly. Let me check the script:
Fixed. The issue was that your ENTRYPOINT referenced package.sh without an absolute path. When bash runs with that ENTRYPOINT, it's in /data/packaging but package.sh wasn't in the shell's PATH. I changed it to use the full path /data/packaging/package.sh and added a chmod +x to ensure it's executable. Rebuild your image and the container should find the script now.**
After the fixed was applied by Gordon, I had different errors at the end of compiling.
I suspect I have an issue with my setup, where the working directory is not being set correctly in the shell.
End of docker file below that's not working for me.
**# The packaging dir is mounted here
WORKDIR /data/packaging
ENTRYPOINT ["/bin/bash", "package.sh"]**
Can you please advise?
Many thanks
Steve