Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker: Prettify comment sections in Dockerfile and Dockerfile.ephemeral. #2117

Closed
1 task
Bidon15 opened this issue Jul 18, 2023 · 2 comments · Fixed by #3145
Closed
1 task

docker: Prettify comment sections in Dockerfile and Dockerfile.ephemeral. #2117

Bidon15 opened this issue Jul 18, 2023 · 2 comments · Fixed by #3145
Assignees
Labels
good first issue Good for newcomers ice-box this label is automatically applied to all issues. it is removed after starting work

Comments

@Bidon15
Copy link
Member

Bidon15 commented Jul 18, 2023

          It's a copy-cat from Dockerfile and Dockerfile.ephemeral. 

I guess a follow-up PR will fix other Dockerfiles.

Editing this one, tho

Originally posted by @Bidon15 in #2052 (comment)

Tasks

@Bidon15 Bidon15 added good first issue Good for newcomers docker labels Jul 18, 2023
@evan-forbes evan-forbes added the ice-box this label is automatically applied to all issues. it is removed after starting work label Feb 27, 2024
@rootulp
Copy link
Collaborator

rootulp commented Mar 4, 2024

There is no longer Dockerfile.ephemeral but there are two Dockerfiles that could use improved comments:

  1. Dockerfile
  2. Dockerfile_txsim

The Dockerfile for testground seem really helpful and could be used for inspiration.

@rootulp rootulp self-assigned this Mar 4, 2024
@rootulp
Copy link
Collaborator

rootulp commented Mar 4, 2024

Honestly going to ignore the txsim Dockerfile for now b/c it's not as important as the other one.

rootulp added a commit that referenced this issue Mar 11, 2024
Closes #2117

I can think of a few follow-ups after reviewing this Dockerfile:

1. Can we use a different username than `celestia`? Perhaps
`celestia-app` to avoid any user name collision with celestia-node.
2. Does `$BUILDPLATFORM` actually get populated?
3. Can we get rid of the hadolint ignore by pinning versions for all the
dependencies?
4. Bump the Alpine version for the BUILDER image
5. `make hadolint` only runs on Dockerfile and not the other Dockerfiles
in this repo

cc: @Bidon15

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
ninabarbakadze pushed a commit to ninabarbakadze/celestia-app that referenced this issue Mar 13, 2024
Closes celestiaorg#2117

I can think of a few follow-ups after reviewing this Dockerfile:

1. Can we use a different username than `celestia`? Perhaps
`celestia-app` to avoid any user name collision with celestia-node.
2. Does `$BUILDPLATFORM` actually get populated?
3. Can we get rid of the hadolint ignore by pinning versions for all the
dependencies?
4. Bump the Alpine version for the BUILDER image
5. `make hadolint` only runs on Dockerfile and not the other Dockerfiles
in this repo

cc: @Bidon15

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
ninabarbakadze pushed a commit to ninabarbakadze/celestia-app that referenced this issue Apr 2, 2024
Closes celestiaorg#2117

I can think of a few follow-ups after reviewing this Dockerfile:

1. Can we use a different username than `celestia`? Perhaps
`celestia-app` to avoid any user name collision with celestia-node.
2. Does `$BUILDPLATFORM` actually get populated?
3. Can we get rid of the hadolint ignore by pinning versions for all the
dependencies?
4. Bump the Alpine version for the BUILDER image
5. `make hadolint` only runs on Dockerfile and not the other Dockerfiles
in this repo

cc: @Bidon15

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
0xchainlover pushed a commit to celestia-org/celestia-app that referenced this issue Aug 1, 2024
Closes celestiaorg/celestia-app#2117

I can think of a few follow-ups after reviewing this Dockerfile:

1. Can we use a different username than `celestia`? Perhaps
`celestia-app` to avoid any user name collision with celestia-node.
2. Does `$BUILDPLATFORM` actually get populated?
3. Can we get rid of the hadolint ignore by pinning versions for all the
dependencies?
4. Bump the Alpine version for the BUILDER image
5. `make hadolint` only runs on Dockerfile and not the other Dockerfiles
in this repo

cc: @Bidon15

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers ice-box this label is automatically applied to all issues. it is removed after starting work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants