Skip to content

Conversation

@Helion55
Copy link

@Helion55 Helion55 commented Feb 1, 2025

Reference Issues or PRs

Fixes #2871

What does this implement/fix?

  • Other (please describe):

Moved docker-images repo back to main nebari's repo. Changes made,

  1. Created folder named docker and moved the necessary files from docker repository.
  2. Updated the .github/workflows folder by adding the build-push-docker.yaml and test-images.yaml files from docker repo's workflow folder.
  3. Added documentation.yml and RFD.md files to .github/ISSUE_TEMPLATE folder.
  4. Updated .pre-commit-config.yaml file.

Testing

  • Did you test the pull request locally?
    no
  • Did you add new tests?
    no

Any other comments?

no

@viniciusdc
Copy link
Contributor

Hey @Helion55 thanks for opening this PR! we will have a look during the following days, in nebari we use pre-commit to lint the files and commit changes; its just a few typos, but if you want then to be self-fixed, you can pip install pre-commit and run pre-commit install that should then run in your next commit. For now, this is the line that currently needs changes:

error: `statis` should be `stasis`, `status`
  --> docker/scripts/install-conda-environment.sh:56:29

@dcmcand dcmcand requested a review from a team as a code owner February 7, 2025 14:49
@dcmcand dcmcand requested review from dcmcand and marcelovilla and removed request for a team February 7, 2025 14:49
@viniciusdc
Copy link
Contributor

Hey, @ Helion55, I am giving you a heads-up on the review status. We are finishing the latest release of Nebari. Once that's out,, we will include this PR on our discussion board next week. Once again, thanks for opening the PR!

@Helion55
Copy link
Author

Thanks @viniciusdc, I was curious about it. I have fixed the thing that you had mentioned. Waiting to catch up on next week.

@@ -0,0 +1,41 @@
# Copyright (c) Nebari Development Team.

Check failure

Code scanning / Trivy

Image user should not be 'root' High

Artifact: docker/Dockerfile.dask-worker
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@@ -0,0 +1,41 @@
# Copyright (c) Nebari Development Team.

Check notice

Code scanning / Trivy

No HEALTHCHECK defined Low

Artifact: docker/Dockerfile.dask-worker
Type: dockerfile
Vulnerability DS026
Severity: LOW
Message: Add HEALTHCHECK instruction in your Dockerfile
Link: DS026
@@ -0,0 +1,41 @@
# Copyright (c) Nebari Development Team.

Check failure

Code scanning / Trivy

Image user should not be 'root' High

Artifact: docker/Dockerfile.jupyterhub
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@@ -0,0 +1,41 @@
# Copyright (c) Nebari Development Team.

Check notice

Code scanning / Trivy

No HEALTHCHECK defined Low

Artifact: docker/Dockerfile.jupyterhub
Type: dockerfile
Vulnerability DS026
Severity: LOW
Message: Add HEALTHCHECK instruction in your Dockerfile
Link: DS026
@@ -0,0 +1,70 @@
# Copyright (c) Nebari Development Team.

Check failure

Code scanning / Trivy

Image user should not be 'root' High

Artifact: docker/Dockerfile.jupyterlab
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@@ -0,0 +1,70 @@
# Copyright (c) Nebari Development Team.

Check notice

Code scanning / Trivy

No HEALTHCHECK defined Low

Artifact: docker/Dockerfile.jupyterlab
Type: dockerfile
Vulnerability DS026
Severity: LOW
Message: Add HEALTHCHECK instruction in your Dockerfile
Link: DS026
@@ -0,0 +1,61 @@
# Copyright (c) Nebari Development Team.

Check failure

Code scanning / Trivy

Image user should not be 'root' High

Artifact: docker/Dockerfile.workflow-controller
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@@ -0,0 +1,61 @@
# Copyright (c) Nebari Development Team.

Check notice

Code scanning / Trivy

No HEALTHCHECK defined Low

Artifact: docker/Dockerfile.workflow-controller
Type: dockerfile
Vulnerability DS026
Severity: LOW
Message: Add HEALTHCHECK instruction in your Dockerfile
Link: DS026
@viniciusdc
Copy link
Contributor

Will start looking into it today

@viniciusdc viniciusdc added the status: in review 👀 This PR is currently being reviewed by the team label Feb 25, 2025
@dcmcand dcmcand requested a review from viniciusdc March 6, 2025 12:09
@dcmcand dcmcand moved this from New 🚦 to In review/QA 👀 in 🪴 Nebari Project Management Mar 6, 2025
@viniciusdc
Copy link
Contributor

Hey @Helion55, I did a quick look at your PR. Since this will be an initial part of a big file move, I would like to disable or not copy the action files initially. Also, we will be making some changes this week in that repo to make things faster to build and more stable overall, so you will probably need to copy/modify the files again.

In the meantime, to not leave you empty-handed, feel free to check any of our issues with Help Needed to Good First Issue labels.

@Helion55
Copy link
Author

Thanks @viniciusdc, Sure, I will do that.

@marcelovilla marcelovilla moved this from In review/QA 👀 to TODO 📬 in 🪴 Nebari Project Management Mar 20, 2025
@Helion55
Copy link
Author

Hello, I have removed those two workflow files; kindly check the PR now. And I apologize for my delayed activity.

@viniciusdc
Copy link
Contributor

Hey @Helion55 sorry I missed your message, thanks. I will need to have a look at this later on...though you might need to copy the files again since a lot has changed in that repo since then

@Helion55
Copy link
Author

Sure @viniciusdc . I'll check and copy them.

@Helion55
Copy link
Author

Hi team, I have updated the branch with the latest commits from nebari-docker-images repo. Kindly check once.

@viniciusdc
Copy link
Contributor

Thanks @Helion55, I will have time next week to look into this

@@ -0,0 +1,52 @@
---
Copy link
Contributor

@viniciusdc viniciusdc Jun 28, 2025

Choose a reason for hiding this comment

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

These template files are not needed

Copy link
Author

Choose a reason for hiding this comment

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

Hi @viniciusdc, is it fine now?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, thanks! I need to take a closer look at what we need to do internally to make this all work from here. I haven't had the time to do so yet, but I plan to check this later today or tomorrow, or next Wednesday.

@viniciusdc
Copy link
Contributor

Hey @Helion55 sorry this got quite shifted, I hope to have some time to look into it this Friday

@viniciusdc
Copy link
Contributor

Also, I suggest you create feature branches in your Fork and create the PRs from those instead of from your main. This gets your git history clean and entirely in sync with ours.

@Helion55 Helion55 closed this by deleting the head repository Oct 30, 2025
@Helion55
Copy link
Author

Hi @viniciusdc, Now I have created a PR for this from a separate feature branch. Kindly check once #3177.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: in review 👀 This PR is currently being reviewed by the team

Projects

Status: TODO 📬

Development

Successfully merging this pull request may close these issues.

[MAINT] - Move docker-images repo back to main nebari's repo

3 participants