Marc A. Modrow
Marc A. Modrow
That's not all the way, where I'd like it to be, but should work fine for the time being.
Question: when you touch the dockerfile&script anyway, wouldn't it be nice to be able to pin the mcc version with some .env variable?
I currently am unable to build the image. ``` docker build -t mccpr2112 . Sending build context to Docker daemon 6.656kB Step 1/4 : FROM mcr.microsoft.com/dotnet/sdk:6.0 ---> 56ae586b64e8 Step 2/4...
That allows to build without buildkit but the container exits instantly anyway. But (after installing the dependencies) I can confirm, that the start-latest.sh works locally.
not tonight. I'll see, when I can get to look at it.
> > not tonight. I'll see, when I can get to look at it. > > Are you running docker commands with sudo? Also, run using `sudo docker-compose run MCC`...
I will as soon as I can, maybe tonight.
I tried `docker system prune -a` and `docker builder prune`. Didn't change the outcome in any way.
I don't have any modifications to your latest build... I'll check it tomorrow. It's late here.
Actually I was stupid enough to run on MCCTeam:master. Correct repo, fresh unchanged pull (`git reset --hard;git pull; docker system prune -a;docker builder prune`) pull: ``` root@:/Docker# docker build -t...