Closed d31337ed closed 7 months ago
I'm uncertain about the meaning of "Dockerfile seems to be corrupted/missing in a new Docker image." The idea of a Dockerfile missing from Docker images is somewhat confusing, as the image is an artifact built using the Dockerfile, which doesn't include the Dockerfile itself.
Here's how you can download Docker Compose and start the container:
As demonstrated, it works seamlessly.
Your first example seems to show an attempt to build from the source, rather than pulling the image. To build it, you should first clone the repository. The section where you mention "To eliminate an error, I've tried to..." also suggests an attempt to build the image, which isn't necessary if you pulled the image first and the image in your compose matches the published one.
Could there be an issue accessing the Docker Hub hosting the image? If so, you might consider changing the image in your compose to one stored on the GitHub registry, such as ghcr.io/umputun/remark42:latest
.
as this is clearly not a bug but rather some sort of confusion, I'll move it to discussions
Hi there!
I've tried to slightly change settings in my copy of
docker-compose.yml
and restart existing instances of remark42 container like I did few times beforeHowever, today I faced an error:
To eliminate an error I've tried to:
docker system prune -a
);docker pull umputun/remark42
);docker-compose.yml
But the issue still appears.For double check I've tried to execute a clean installation from docker image in two independent systems. Having the same issue on a second system:
Steps to reproduce:
docker-compose.yml
from repo: https://github.com/umputun/remark42/blob/master/docker-compose.ymldocker-compose pull && docker-compose up -d
Please review a content of the latest docker image Thank you!