Skip to content

Conversation

@Helion55
Copy link

Reference Issues or PRs

Fixes #2871

What does this implement/fix?

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

@Helion55 Helion55 requested a review from a team as a code owner October 30, 2025 06:32
@Helion55 Helion55 requested review from dcmcand and marcelovilla and removed request for a team October 30, 2025 06:32
@Helion55 Helion55 changed the title enhancement : Moved Docker images repo to docker folder in main branch MAINT : Moved Docker images repo to docker folder in main branch Oct 30, 2025
@@ -0,0 +1,158 @@
FROM ubuntu:24.04 AS builder

Check failure

Code scanning / Trivy

Image user should not be 'root' High

Artifact: docker/Dockerfile
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@Adam-D-Lewis
Copy link
Member

Thanks for separating that work into separate PRs @Helion55. Can you get the "pre-commit" check to pass before we review. Thank you!

@Helion55
Copy link
Author

Helion55 commented Nov 3, 2025

Hi @Adam-D-Lewis, The pre-commit checks are passed. Is it fine to proceed now?

Copy link
Contributor

@dcmcand dcmcand left a comment

Choose a reason for hiding this comment

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

Hi @Helion55,
Thanks so much for this PR. This will be really useful when it is merged. I left specific comments inline, but also want to call out that currently if someone has a branch that includes changes to the images, those updated images will not be used in integration tests. This eliminates the main advantage of this move. Please update the integration tests to use the new images if changes are made to the docker images.

Copy link
Contributor

Choose a reason for hiding this comment

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

Since this change is unrelated to the current issue, please move it out of this pr.

branches:
- "*"
paths:
- "Dockerfile"
Copy link
Contributor

Choose a reason for hiding this comment

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

These paths won't work for this repo


on:
pull_request:
paths:
Copy link
Contributor

Choose a reason for hiding this comment

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

These paths won't work with this repo

- name: "Build docker images 🐳"
uses: docker/build-push-action@v3
with:
context: .
Copy link
Contributor

Choose a reason for hiding this comment

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

This context is not correct for this repo

- name: Build Image 🛠
uses: docker/build-push-action@v3
with:
context: .
Copy link
Contributor

Choose a reason for hiding this comment

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

This context is incorrect for this repo

dockerfile:
- jupyterlab
- jupyterhub
- dask-worker
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason that you aren't including nebari-workflow-controller here?

Copy link
Contributor

Choose a reason for hiding this comment

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

Line 67 of this file in now out of date and should be updated.

Copy link
Contributor

Choose a reason for hiding this comment

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

References to the old docker repo need to be updated here

on:
pull_request:
paths:
- "Dockerfile.*"
Copy link
Contributor

Choose a reason for hiding this comment

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

This path is incorrect, there is a single dockerfile, so Dockerfile.* will never match

@github-project-automation github-project-automation bot moved this from New 🚦 to Changes requested 🧱 in 🪴 Nebari Project Management Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Changes requested 🧱

Development

Successfully merging this pull request may close these issues.

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

3 participants