dockware
  • dockware doc's
  • News
  • Setup
    • Docker Setup
    • What Image should you use?
    • Performance Tweaks
  • Use Dockware
    • First Run
    • Update Dockware
    • Advanced Run
    • Default Credentials
    • Symfony or Shopware 5
    • Changelog
  • Features
    • Intro
    • Environment Variables
    • Adminer
    • Mailcatcher
    • Switch PHP Version
    • Switch Node Version
    • Tideways Profiling
    • Pimp my Log
    • Filebeat
    • SSH Users
    • MySQL Users
    • Shopware Currency
  • Development
    • Intro
    • Start Developing
    • Switch Branches
    • Debugging
    • Watchers
    • App Development
    • Update Shopware
    • Dockware Essentials
    • Custom Domains
    • Custom Images
    • Code Coverage
    • CLI Build Shopware 6 Plugin
    • Multi-Environment Setups
  • Contribute
    • Intro
    • Setup Github Version
    • Create Feature
    • Code Styles
    • Testing
    • Create Pull Requests
  • CI/CD
    • Github
    • Gitlab
    • Bitbucket
    • Buddy
  • Tips & Tricks
    • Create a new Project
    • Bind-Mounting
    • Persisting Data
    • Housekeeping
    • Online Servers
    • Performance on Mac
    • Security
  • FAQ
    • Sequel Pro
    • Dockware and other images
    • Scripts (PSH?)
    • Redis
    • Error Port not available
    • MySQL failed
    • Elasticsearch
    • Windows Problems
    • Chrome Problems
    • Import MySQL Dump
    • Shopware 5 Support
    • Use Https/SSL
    • Container hangs in Pipeline
    • Disable the admin worker
  • Additional Links
    • Imprint
    • Founders
    • Dockware website
    • Dockware in Shopware Slack
Powered by GitBook
On this page

Was this helpful?

  1. FAQ

Windows Problems

Can't connect into container on Windows

If your terminal says that you don't have a tty or interactive terminal, you might want to prefix winpty which should work for you:

ON HOST
winpty docker exec -it shopware bash

System cannot find the path specified in "docker cp".

Some directories and paths are long in Shopware...really long :). Unfortunately Windows might tell you this too. The good thing is, there's a fix for long file names.

Please try these things:

  • Move your project to C:\ which might shorten things automatically if you've had a deeper directory before.

  • If you are on Windows 10, you can enable long paths. Open the Computer Configuration > Administrative Templates > System -> Filesystem > Enable NTFS long paths. You can also modify the corresponding registry entry HKLM\SYSTEM\CurrentControlSet\Control\FileSystem to LongPathsEnabled (Type: REG_DWORD) to remove most of the MAX_PATH limitations.

Problems with log path via docker cp

As this is a problem in combination with 1. docker 2. shopware file structure 3. Windows we can't fix this for you, but we can work a bit around it

  1. you have to open your terminal "cmd" with admin rights.

  2. it's possible that also long paths does not work so there will be some folder which can't be downloaded. In this case we recommend zipping the content within the container, copy and unzip:

    2.1 docker exec -it CONTAINERNAME zip -r dockware.zip ./

    2.2 docker cp CONTAINERNAME:/var/www/html/dockware.zip C:\my\path\dockware.zip

  3. right click zip file -> unzip

the unzip process will show you some notifications that file XY can't be extracted as of path length, please skip this files to get all others to your local path.

PreviousElasticsearchNextChrome Problems

Last updated 3 years ago

Was this helpful?