Skip to content

Improve the "provisioning" script (setup-system.sh) #869

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

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

tokk-nv
Copy link
Collaborator

@tokk-nv tokk-nv commented Feb 21, 2025

  • Make script current-directory-agnostics
  • Handle other Jetson (other than Jetson AGX Orin)
  • Handle Jetson with L4T entirely installed on SSD (no need to mount)
  • Install Docker

@OriNachum
Copy link
Collaborator

@tokk-nv
Thank you for improving it!

I will run it locally (On Super Nano - it was originally written on it) tonight.
Do you plan to fix all checkboxes in this PR, or make a series of PRs?

@OriNachum
Copy link
Collaborator

@tokk-nv
While at it, I'm running it "fresh" on AGX Orin and I found some issues:

  1. File .env and .env_sample are on root, but the script is in the scripts folder.
  2. The script runs on loops.
  3. Changes not applied: zram, swap, docker.
  4. List of power options are for Super Nano, not AGX Orin.

Should I wait for your changes, merge to yours, or merge to original?

@dusty-nv
Copy link
Owner

@OriNachum I'll ping Chitoku tomorrow to either get back to you about this or turn you loose on it.

The other scripts like build.sh and run.sh will move under scripts/ too, we had previously attempted it and had to revert until some docs get updated, but it was not just your scripts that I was hiding away under there.

The discussion about the .env location...

There will also be a static copy of the docker-compose templates exported under stacks/ in the repo, parameterizable by .env

Should they be the same .env then? Or not because they are separate processes, one is a one-time setup, the other is everytime a stack gets run.

@OriNachum
Copy link
Collaborator

@dusty-nv @tokk-nv I saw Chitoku already merged? I have the continuation of the PR and pending review of both/either

Split to each domain, and easy to add docker install, too.
It's tested on agx-emmc, agx-emmc-nvme and agx-nvme
I want to merge before continuing

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.

3 participants