I'm not familiar with docker compose and I don't usually use it: I prefer to build images via docker build and launch my containers via systemd services. In a case like this I try to dissect the docker-compose.yml then I build and launch my containers in the "traditional" way.
I'm trying to install AUTOMATIC1111. If I understood correctly, I need
the image corresponding to the "download" service to initialize the contents of the "data" folder: I was able to build it and make it work without problem
the image corresponding to the "auto" service: this is where I have a problem, I cannot build it.
I do docker build --progress plain -t test-a1111:latest ./services/AUTOMATIC1111/ on the release 9.0.0 files
I haven't found any trace of this problem in other issues despite the large number of users, so I wonder if this is due to not using docker compose? Am I supposed to be able to construct the image this way? If yes how, and if not why?
Hi,
I'm not familiar with docker compose and I don't usually use it: I prefer to build images via
docker build
and launch my containers via systemd services. In a case like this I try to dissect the docker-compose.yml then I build and launch my containers in the "traditional" way.I'm trying to install AUTOMATIC1111. If I understood correctly, I need
I do
docker build --progress plain -t test-a1111:latest ./services/AUTOMATIC1111/
on the release 9.0.0 filesHere is the result :
I haven't found any trace of this problem in other issues despite the large number of users, so I wonder if this is due to not using docker compose? Am I supposed to be able to construct the image this way? If yes how, and if not why?
I'm using docker
27.0.3
on a Debian 12 system.