proxigram/proxigram
11
75
Fork 7
Code Issues 11 Pull requests Packages Projects Releases Wiki Activity

Can't build docker image with current Dockerfile #42

New issue
Open
opened 2024-03-22 23:31:13 +00:00 by CapgrasDelusion · 10 comments
CapgrasDelusion commented 2024-03-22 23:31:13 +00:00
Copy link

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.

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.
👍 1
Undercut0150 commented 2024-03-23 19:57:50 +00:00
Copy link

Popping in to say this is also happening on my machine.

here are the commands I run

git checkout main
git pull
sudo docker compose build proxigram
Popping in to say this is also happening on my machine. here are the commands I run ``` git checkout main git pull sudo docker compose build proxigram ```
👍 1
nyuuzyou commented 2024-04-21 12:52:58 +00:00
Copy link

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.

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:

- ready started server on 0.0.0.0:3000, url: http://localhost:3000
Error: connect ECONNREFUSED 127.0.0.1:34361
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 34361
}
Error: connect ECONNREFUSED 127.0.0.1:34361
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 34361
}
> 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. 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: ``` - ready started server on 0.0.0.0:3000, url: http://localhost:3000 Error: connect ECONNREFUSED 127.0.0.1:34361 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 34361 } Error: connect ECONNREFUSED 127.0.0.1:34361 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 34361 } ```
👍 1
dominion commented 2024-04-24 12:52:21 +00:00
Copy link

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 | }

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 | }
👍 1
KaKi87 commented 2024-05-04 11:02:06 +00:00
Copy link

https://proxigram.ducks.party/ redirects here 👀

https://proxigram.ducks.party/ redirects here 👀
👍 1
nyuuzyou commented 2024-05-04 13:16:40 +00:00
Copy link

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.

> 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.
👍 1
dominion commented 2024-05-14 13:26:52 +00:00
Copy link

Should we switch off the service or is there fix? ;)

Should we switch off the service or is there fix? ;)
👍 1
nyuuzyou commented 2024-05-14 15:35:32 +00:00
Copy link

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

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
👍 1
KaKi87 commented 2024-05-15 12:01:22 +00:00
Copy link

If this is a build error, wouldn't it be possible to checkout parent commits until build works ?

If this is a build error, wouldn't it be possible to checkout parent commits until build works ?
👍 1
nyuuzyou commented 2024-05-15 12:08:36 +00:00
Copy link

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.

The build problem can be solved by the issue author's method. But you will not be able to start proxigram anyway.

> 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. The build problem can be solved by the issue author's method. But you will not be able to start proxigram anyway.
👍 1
ThePenguinDev commented 2024-05-16 18:18:59 +00:00
Owner
Copy link

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.

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.
👍 2 ❤️ 1 🎉 1
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: proxigram/proxigram#42
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?