Docker Image Won't Start on Windows – "unknown shorthand flag: 'f'" and "unknown command: docker compose" Errors

[haox5776-maker]

Hello everyone,
I’m encountering an issue with Docker on Windows where I cannot start Docker images manually, despite having them available locally. I’d appreciate any guidance on how to resolve this.
Problem:
When I run the setup or initialization script (or try commands manually), I receive multiple errors in the CLI:
unknown shorthand flag: 'f' in -f​ – This appears when the script attempts to pull Docker images or start services.
docker: unknown command: docker compose​ – After waiting for services, it seems the docker composecommand is not recognized. This is followed by an error stating the simnibsservice is not running.
A typical error output looks like this:
Current project directory: /mnt/f/sourcedata/
Press Enter to use this directory or enter a new path:
Pulling required Docker images...
unknown shorthand flag: 'f' in -f
Usage: docker [OPTIONS] COMMAND [ARG...]
...
Starting services...
unknown shorthand flag: 'f' in -f
...
Waiting for services to initialize...
docker: unknown command: docker compose
Run 'docker --help' for more information
Error: simnibs service is not running. Please check your docker-compose.yml and container logs.
What I’ve checked/tried:
Docker Desktop is running, and images are listed locally.
I’ve confirmed Docker is installed and the daemon is accessible.
Basic dockercommands (like docker imagesor docker ps) work, but the specific docker composecommand fails.

[idossha]

Hi @haox5776-maker, sorry to hear about the problem, and happy you reached out.

Going to ask a few question to try and remote debug the problem.

1. Does it give you the same problem with v2.2.0?
2. Do you have the latest version of the loader.sh script?
3. Do you have the latest version of Docker installed on your machine?

I sense it may be an issue with the docker compose command that are not compatible with your system. Before we go to modify the script I want to ensure that you have the system set for your Windows - Docker integration.

Step 1:
Open Docker Desktop
Go to Settings → Resources → WSL Integration
Make sure you enable integration with your default bash based terminal.
Click Apply & Restart

Then inside terminal run: docker compose version. If this works, your script should now run correctly.

Step 2:
If above does not solve it, try to change all the docker compose commands to the legacy docker-compose command, and that may solve the issue.

Please let us know if any of the above solves it or not. In any case, I will be releasing a new version tomorrow that have a much more robust approach for the desktop application, specifically for Windows.

Ido

[idossha]

p.s. I just ran a simple test on a Windows machine and I was not able to replicate your issue. So please make sure all elements are updated to the latest versions. i.e. TI-Toolbox scripts and Docker installation. Should solve the problem.

[haox5776-maker]

Hi Ido,

Thank you very much for the detailed response and for taking the time to help troubleshoot this issue. I really appreciate your support.

I wanted to provide you with an update on my side. I was able to successfully run the application using the TI Toolbox automatic initialization tool, and in that case everything worked as expected.

However, when I try to run the loader.sh script manually, it still does not work. The behavior and error are the same as before, so it seems the underlying issue with loader.sh remains unresolved.

I have verified that:

Docker Desktop is up to date

Docker–WSL integration is enabled as you described

docker compose version runs correctly in the terminal

Given this, it still appears that the problem is specifically related to how loader.sh invokes Docker / Docker Compose on my system.

Thank you again for looking into this, and I am looking forward to trying the new version you mentioned for Windows when it is released.

Best regards,
Hunter

[idossha]

Thanks for the update Hunter. So to clarify, you are able to launch the toolbox via the desktop application but not through the loader.sh script? What terminal are you using? WSL or Ubuntu? In any case, if there is a particular reason you need to use the loader.sh specifically, I am happy to schedule a virtual session and try to troubleshoot online.

Best,
Ido

[idossha]

Again, to make sure we are on the same page, see screenshot below.

[idossha]

Hi @haox5776-maker,

Checkin in to see if issue has been solved.