D2 cli not seeding appropriately [FIXED]

Development - Développement App Development
1

Hi everyone,

I’m having an issue trying to seed a new d2 cluster with my own sql file. The example code is:

d2 cluster up pivottest \
--dhis2-version 2.40.3 \
--seedFile <path-to-sql>

It is returning the following error message:

/bin/sh: 1: ./scripts/seed.sh: not found
 [DEBUG ERROR] ./scripts/seed.sh exited with non-zero exit code (127).

This has worked fine in the past with this exact file, so I suspect it is maybe due to a mismatch of yarn/npm/docker versions on my machine, but I haven’t been able to pinpoint the problem.

I am able to seed from the demo.

Any thoughts on the issue or a workaround? I have been thinking about just using docker compose directly to get around the d2 issue.

System specs:
OS: Ubuntu 22.04.5 LTS x86_64

❯ docker --version
Docker version 27.5.1, build 9f9e405
❯ yarn -v
4.6.0
❯ d2 -v
5.0.1
2

Hey @mv_evans! Thanks for reporting this – we’ve noticed this on our side too, and we’re taking a look into how to fix it

We’ve opened up this issue to track it: Jira

We’ll update you on any findings!

2 Likes
3

Hey again @mv_evans! We made a fix in the underlying docker tools (thanks @austin), so you should be able to run d2 cluster up again, this time with the --update flag to update the affected files (you won’t need to update the d2 CLI, probably)

Let us know if that works for you! :slightly_smiling_face:

2 Likes
4

Hello!

Yup, that fixed it for us. :partying_face:

Thank you so much for responding to this so quickly. We really appreciate it!

2 Likes