Hi, @Germs31, would you please send us a link to the build logs? For example, a link like the one below:
My best guess is that there is a difference in letter case in some reference to this file.
For example:
../../../images/inside-shop-dark.jpg
in /opt/build/repo/src/pages/style/Index
is this file:
/opt/build/repo/src/images/inside-shop-dark.jpg
The first part of that path is the base of the repo (where it is cloned to) on the build system. So let’s just ignore this part:
/opt/build/repo
So, were are looking for in this repo:
./src/images/inside-shop-dark.jpg
Here is the issue I suspect you are experiencing:
- The letter case of the file on the disk differs from the letter case in the site code.
For example, if the location on disk is actually this (with a upper-case letter “I” in “Images”):
./src/Images/inside-shop-dark.jpg
On MacOS, this will work. Images
and images
are the same. On Linux (the build system uses Linux), this these are two different directories and will generate an error.
Here is a quick example on MacOS:
$ echo "there is only one file" > Example.txt
$ cat Example.txt
there is only one file
$ cat example.txt
there is only one file
$ ls -l *
-rw-r--r-- 1 luke staff 52 Jul 22 22:31 Example.txt
This shows that there is a single file but you can get the contents with both Example.txt
and example.txt
on MacOS.
However, on Linux you get an error with example.txt
:
$ echo "there is only one file" > Example.txt
$ cat Example.txt
there is only one file
$ cat example.txt
cat: example.txt: No such file or directory
$ ls -l
total 4
-rw-rw-r-- 1 luke luke 52 Jul 23 05:32 Example.txt
To summarize, please check for case sensitivity issue and, if that doesn’t resolve, a link to the build would be helpful.