Hello, i cannot develop on windows, because get blank screen. When i open console i get this errors: (X) ember_jquery.js?1579775136.5740232:1 Uncaught Error: Errno::EEXIST: File exists @ dir_s_mkdir - /var/discourse/tmp/cache/assets/sprockets/v3.0/pr (in /home/gaijinsailor/.rbenv/versions/2.6.2/lib/ruby/2.6.0/fileutils.rb:239:in `mkdir') at ember_jquery.js?1579775136.5740232:1 and alot of similar errors. So, basically, discourse cannot load scripts. When i open script in separate window i get following error: Script: http://localhost:3000/assets/locales/en_US.js?1579775136.5398135 Body: throw Error("Errno::EEXIST: File exists @ dir_s_mkdir - /var/discourse/tmp/cache/assets/sprockets/v3.0/x2\n (in /home/gaijinsailor/.rbenv/versions/2.6.2/lib/ruby/2.6.0/fileutils.rb:239:in `mkdir')") So i start digging, and i realized that problem is with sprockets. I mounted disourse dir from windows to docker, and filesystem is case insensitive. And sprockets seems like work only on linux like filesystems (like ext4) which can make dir case sensitive. Is there any solution to this problem? Thanks UPD: this issue with sprockets is documented on github: FileStore cache patch in v3.6 causes directory name collisions in Windows · Issue #283 · rails/sprockets · GitHub but issue is still open, and no solution :frowning:

Funny @pixeltrix came across this yesterday and used this hack to work around it: Allow overriding of the default sprockets cache path committed 12:09PM - 27 Jan 20 UTC (UTC) [image] pixeltrix +12 -0 Sprockets 3.0 and later uses Base64 digests for cache paths and these present pr…oblems when used with NTFS on Windows which is case-insensitive. By allowing the overriding of the cache path from an environment variable we can use a Docker volume to cache the asset compilation. This is actually faster on both Mac and Windows than the default path. I recommend just installing WSL2 and using our WSL2 setup which is far faster and easier to reason about: [image] Install Discourse on Windows for development Developer Guides information_source This tutorial has been tested on Windows 10 and 11. To set up a development environment for Discourse on Windows, you can do it using Windows Subsystem for Linux feature. This setup requires the WSL 2 installation. It is only available in Windows 10 builds 18917 or higher. We’ll assume that you already installed Windows Subsystem for Linux 2 (Ubuntu) on your Windows 10 system. WARNING: Install Ubuntu 18.04, and not 20.04 since some installations will fail on 20.04. For m… Installation of dev environment is trivial, you just get WSL2 going, install docker, and then use our docker dev setup. [image] Install Discourse for development using Docker Developer Guides Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development container. white_check_mark Pros: No need to install any system dependencies, no configuration needed at all for setting up a development environment quickly. x Cons: Will be slightly slower than the native dev environment on Ubuntu, and much slower than a native install on MacOS. See also Developing Discourse using a Dev Container …

Problem with development on Windows with Docker and mounted volume

Development

Nikolay (Nikolay) January 28, 2020, 10:10am 3

Thank you very much. Hack worked.
Later i will try to use WSL2

Topic		Replies	Views
Install Discourse for development using Docker Developer Guides docker , dev-install , how-to	226	94771	May 22, 2026
Trouble setting up dev Discourse on WSL2 with Docker - solved Development	3	835	October 30, 2021
Discourse on WSL attempting to use /var/lib/docker instead of connecting to Docker Desktop on host Self-hosting dev-install	5	281	October 10, 2026
Does discourse support docker on windows? Self-hosting docker	6	5159	June 1, 2018
Installation notes for Discourse on Bash for Windows Development	17	14020	August 23, 2018

Problem with development on Windows with Docker and mounted volume

Related topics