Skip to content

Conversation

@andrei-21
Copy link
Contributor

  • run the actual binary (cargo run will build a develop binary)
  • copy only neccesary files during docker build
  • do not expose port 8000 since it is not used by the binary

* run the actual binary (cargo run will build a develop binary)
* copy only neccesary files during docker build
* do not expose port 8000 since it is not used by the binary
- BITCOIN_REST_PORT=8332
- BITCOIN_REST_PATH=/rest/
command: 'cargo run'
command: 'rapid-gossip-sync-server'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see anywhere where the actual binary is built, though? Shouldn't we instead do cargo run --release?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is built in docker at

RUN cargo install --path .

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! Presumably we should drop the EXPOSE 8000 from that file as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is what I did as well ;)

@TheBlueMatt TheBlueMatt merged commit 2b60838 into lightningdevkit:main Apr 29, 2025
4 checks passed
@andrei-21 andrei-21 deleted the fix/docker-confusions branch April 29, 2025 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants