Skip to content
Snippets Groups Projects
New look: Off

drush sql-cli < dump.sql didn't work

    • Open Issue created by Dejan @dejan-acolono

    but here is how to do it in an alternative way:

    docker-compose exec -T php drush sql-cli < drupal.sql

    image

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • jurgenhaas
      jurgenhaas @jurgenhaas ·
      Owner

      Yes, pipes don't work in this scenario because the script drush calls a container and that process inside the container can't read from the pipe. We went away from using pipes completely, so <, > or | are not used at all.

      For the above use case, there is even a better one: drush sql-cli --file=drupal.sql

    • Dejan
      Dejan @dejan-acolono ·
      Author

      okay, thanks for that. All good then

    • jurgenhaas
      jurgenhaas @jurgenhaas ·
      Owner

      Just for the records and if others ever come across this issue, what's the difference between drush sql-cli < dump.sql and docker-compose exec -T php drush sql-cli < drupal.sql where the first fails and the second succeeds:

      drush sql-cli < dump.sql is executed in the l3d container, so the pipe runs in l3d, but drush switches context into the PHP container. So, the process and the pipe are "on different hosts" so to speak.

      docker-compose exec -T php drush sql-cli < drupal.sql on the other hand takes drush sql-cli < drupal.sql together into the PHP container, so that process and pipe are running on the same host. And that's why this one works.

    • jurgenhaas added Documentation label

      added Documentation label

    • GitLab Bot
      GitLab Bot @gitlab-bot ·
      Maintainer

      EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.

      DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.

    • GitLab Bot
      GitLab Bot @gitlab-bot ·
      Maintainer

      EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.

      DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.

    • GitLab Bot added dormant label

      added dormant label

    • jurgenhaas removed dormant label

      removed dormant label

    • GitLab Bot
      GitLab Bot @gitlab-bot ·
      Maintainer

      EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.

      DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.

    • GitLab Bot added dormant label

      added dormant label

    • danielspeicher removed dormant label

      removed dormant label

    • GitLab Bot
      GitLab Bot @gitlab-bot ·
      Maintainer

      EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.

      DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.

    • GitLab Bot added dormant label

      added dormant label

    • jurgenhaas removed dormant label

      removed dormant label

    • GitLab Bot
      GitLab Bot @gitlab-bot ·
      Maintainer

      EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.

      DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.

    • GitLab Bot added dormant label

      added dormant label

    • jurgenhaas removed dormant label

      removed dormant label

    Please register or sign in to reply