2020-11-22 16:09:29
I think what I am doing wrong is not using volumes more

Fireduck
2020-11-22 16:10:27
And I would get the error touching files created within a docker environment from outside the environment

Fireduck
2020-11-22 16:43:02
the intermarrying of outside to inside is rough on docker

Rotonen
2020-11-22 16:43:32
rather do a second container and attach same volume to both in docker-compose

Rotonen
2020-11-22 16:45:44
Yeah, for a new project I did the extra container to interact with files.

Fireduck