Can't build docker image with current Dockerfile #42
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To start, this very much might be user error. The only image I've ever built is Proxigram. I managed to do it successfully in the past but ran into this today.
When trying to build the current setup via docker-compose.yaml and the current Dockerfile it would fail with the error "failed to solve: source can't be a git ref for COPY"
If, in the Dockerfile, I comment out the line:
COPY --from=build-env /app/.git /app/.git
it builds and still somehow seems to work... Again, this might just be me but figured I'd post in case it's not.
Popping in to say this is also happening on my machine.
here are the commands I run
The problem is reproducible for me. However, after successfully building the image after starting the container, the instance responds with "Internal Server Error" to all requests.
Logs:
same here
proxigram | Error: connect ECONNREFUSED 127.0.0.1:38645
proxigram | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
proxigram | errno: -111,
proxigram | code: 'ECONNREFUSED',
proxigram | syscall: 'connect',
proxigram | address: '127.0.0.1',
proxigram | port: 38645
proxigram | }
https://proxigram.ducks.party/ redirects here 👀
You're right. Due to issues on the Proxigram code side, the instance is now not working correctly. This is the best idea that I have come up with at the moment.
Should we switch off the service or is there fix? ;)
I have tried to determine the cause of the problem, but have been unsuccessful. I have no choice but to place a redirect to this issue instead of the instance
If this is a build error, wouldn't it be possible to checkout parent commits until build works ?
The build problem can be solved by the issue author's method. But you will not be able to start proxigram anyway.
I'm really sorry that so many things are not working, I haven't had the time to fix a lot of this problems, and to be honest, my current laptop is not the best to be testing all build tools are working. I will dedicate more time to fix so many issues that have come along as much as I can, update dependencies, rewrite/refactor the codebase, and more.