Not sure what I did here... I've been building and...
# docker
s
Not sure what I did here... I've been building and testing images on my Windows machine and running them on a Digital Ocean droplet. The current image works fine on Windows, however, when I run it on the Ubuntu droplet, I get the following...
Copy code
[INFO] 2023-09-25T18:17:54Z - CF Engine defined as lucee@5.3.10+120
[INFO] 2023-09-25T18:17:54Z - Server Home Directory set to: /usr/local/lib/serverHome
[INFO] 2023-09-25T18:17:54Z - Generating server startup script
dirname: missing operand
Try 'dirname --help' for more information.
Error: Unable to access jarfile server
[INFO] 2023-09-25T18:17:54Z - 
[INFO] 2023-09-25T18:17:54Z - Starting server using generated script: /usr/local/bin/startup.sh
mv: cannot stat '/app/server-start.sh': No such file or directory
Anyone run into this issue? Does this have to do with something in my Docker file?
b
Usually this indicates an invalid combination of env vars on the container. cc/ @jclausen
j
Very likely. Is that error during the build of your custom Docker image or at runtime?
Does your
server.json
have any hard-coded windows paths in it or paths that are invalid in the case-sensitive ’Nix environment?
s
No, it builds without issue and I can run the container on Windows. It's when I try to run on my Digital ocean droplet. Actually, I just tried spinning up a container using "ortussolutions/commandbox:latest" and I'm getting the same thing. I wonder if it has to do with an older version of Docker running on my droplet?
j
It could.
If you are running Docker 18 on an older Ubuntu version, you can’t use the latest image version.
s
OK, I'll check into it. Thanks!
That'll be for tomorrow, though. time to head home. :)
I was still logged in... I'm running Docker 19.03.2 on Ubuntu 18.04.3
j
You will probably need to roll back to image version 3.6.4 - which was Ubuntu Focal. After that, the base image was running on Jammy.
👍 1
I had the same issue with a client recently and the solution was the same, until we updated their infrastructure.
s
OK, thank you! I have other droplets with different versions of docker (didn't realize)... that's another reason for my confusion... latest works on other droplets.
🙂 1