The -v option seems to behave differently with Docker for Windows, wherein
-v $(pwd)/config.ini:/usr/src/app/config.ini acts like mkdir /usr/src/app/config.ini
A possible workaround was bind mounting a folder structure like this:
project dir/
└─ config/
├─ config.ini
└─ bot.session
using -v $(pwd)/config:/usr/src/app/config (and changing the source to use this folder).
However, this STILL creates /usr/src/app/config/config.ini/ as a folder.
I am unsure how to solve this without creating the config file in the image, which defeats the purpose of the relevant check in the source
The
-voption seems to behave differently with Docker for Windows, wherein-v $(pwd)/config.ini:/usr/src/app/config.iniacts likemkdir /usr/src/app/config.iniA possible workaround was bind mounting a folder structure like this:
using
-v $(pwd)/config:/usr/src/app/config(and changing the source to use this folder).However, this STILL creates
/usr/src/app/config/config.ini/as a folder.I am unsure how to solve this without creating the config file in the image, which defeats the purpose of the relevant check in the source