Jetson Nano as Onboard Computer

Blue Robotics Software BlueOS
21

Hello, I am working on replacing the raspberry pi with a jetson nano on our bluerov2.
After reading related posts, I ensured the username is pi and the hostname is localhost, I then ran the installation script (from https://github.com/bluerobotics/BlueOS/tree/master/install) on my jetson nano.
The installation completed successfully, but I am unable to access http://blueos.local from my computer.

Attached below are the docker logs containing error:

2026-01-24 08:02:04.334 | INFO     | main:update_swap_size:634 - Checking and updating swap size…
2026-01-24 08:02:04.812 | INFO     | commonwealth.utils.commands:run_command:73 - Host: ‘cat “/etc/dphys-swapfile”’ : returned 1
2026-01-24 08:02:04.813 | ERROR    | commonwealth.utils.commands:run_command:79 - stderr: cat: /etc/dphys-swapfile: No such file or directory

2026-01-24 08:02:04.815 | ERROR    | main:update_swap_size:651 - Could not find CONF_SWAPSIZE in configuration
2026-01-24 08:02:04.816 | INFO     | main:update_cgroups:248 - Running cgroup update..
2026-01-24 08:02:05.289 | INFO     | commonwealth.utils.commands:run_command:73 - Host: ‘cat “”’ : returned 1
2026-01-24 08:02:05.289 | ERROR    | commonwealth.utils.commands:run_command:79 - stderr: cat: ‘’: No such file or directory

2026-01-24 08:02:05.808 | INFO     | commonwealth.utils.commands:run_command:73 - Host: ‘sudo cp “” “.before_update_cgroups.bak”’ : returned 1
2026-01-24 08:02:05.809 | ERROR    | commonwealth.utils.commands:run_command:79 - stderr: cp: cannot stat ‘’: No such file or directory

2026-01-24 08:02:05.810 | DEBUG    | commonwealth.utils.commands:upload_file:141 - uploading to
2026-01-24 08:02:06.377 | DEBUG    | commonwealth.utils.commands:upload_file:149 - CompletedProcess(args=[‘scp’, ‘-i’, ‘/root/.config/.ssh/id_rsa’, ‘-o’, ‘StrictHostKeyChecking=no’, ‘/tmp/file_to_upload’, ‘pi@localhost:/tmp/uploaded_file’], returncode=0, stdout=‘’, stderr=‘’)
2026-01-24 08:02:06.886 | WARNING  | commonwealth.utils.commands:run_command:71 - Failed to run command with SSH key. Command '[‘sshpass’, ‘ssh’, ‘-i’, ‘/root/.config/.ssh/id_rsa’, ‘-o’, ‘StrictHostKeyChecking=no’, ‘pi@localhost’, 'sudo mv /tmp/uploaded_file ‘]’ returned non-zero exit status 1., trying with sshpass:
sudo mv /tmp/uploaded_file
Error: unable to set logging path: Unable to connect to any of [tcp/127.0.0.1:7447]!  at /root/.cargo/git/checkouts/zenoh-9c599d5ef3e0480e/b70ee93/zenoh/src/net/runtime/orchestrator.rs:367.
2026-01-24 08:02:07.358 | ERROR    | main::805 - An error occurred while applying patches: Command '[‘sshpass’, ‘-p’, ‘raspberry’, ‘ssh’, ‘-o’, ‘StrictHostKeyChecking=no’, ‘pi@localhost’, 'sudo mv /tmp/uploaded_file ‘]’ returned non-zero exit status 1.
Using host’s resolv.conf instead of the one from the docker
SSH is working
mkdir: cannot create directory ‘/sys/fs/cgroup/system.slice/docker-2d390d98afa392d7e63ec23e2864943b60c9dede9cf8e9a98b13cc02dc4bbdfb.scope/child_cgroup’: No such file or directory
Docker cgroups root: system.slice/docker-2d390d98afa392d7e63ec23e2864943b60c9dede9cf8e9a98b13cc02dc4bbdfb.scope
Creating a new child cgroup…

Thanks in advance for your help. Please let me know if you need more details.

22

Hi everyone, just checking in to see if anyone has had a chance to look at this? I’m still stuck on the BlueOS installation on my Jetson Nano. If there’s any other specific log file or info I should provide to help troubleshoot, please let me know!

23

Hi @Todd, welcome to the forum :slight_smile:
I’ve moved your post here, as it’s on the same topic as this thread.

The BR team generally isn’t well-versed in Nvidia Jetson hardware usage, beyond what’s already been discussed on this forum. Our main relevant person is away right now, and the rest of us don’t have the time or resources available to start investigating a custom setup like that independently

  1. What kind of computer are you using?
  2. How are you trying to access BlueOS (including what browser)?
  3. Have you done any kind of network configuration to enable that, or is it possible you have a firewall configuration that blocks HTTP requests, for example?
  4. What do you mean by “unable to access”?

From the logs you attached, it’s not obvious to me that it’s not working - just that some of the standard steps didn’t work quite as anticipated for a Raspberry Pi.

24

Hi @Eliot,

Update: I’ve managed to get BlueOS running on Jetson Nano by bypassing the standard bootstrap and manually running the core container with modified parameters.

The root cause is that the official bootstrap script fails on Jetson’s Kernel 4.9 due to Cgroup hierarchy differences and missing Pi-specific files (like dphys-swapfile).

The manual fix that worked for me:

Stop/Remove blueos-bootstrap (it keeps overwriting custom configs with incompatible Pi-defaults).

Manually run blueos-core with:

    --privileged

    -v /sys/fs/cgroup:/sys/fs/cgroup:rw (Fixes the mkdir / cgroup error)

    --net=host

Since BlueOS is now fully accessible at http://localhost, it confirms the issue is the hardware-specific “system patching” logic. Is there a plan to allow a “Generic Linux” flag in the installer to skip these Pi-only steps?

To answer your questions:

  1. My Windows laptop.
  2. I tried access with ip adress directly on my firefox, and the blueos.local url. Additionally, I tried curl localhost:80 on my jetson nano.
  3. Yes, I made sure all ports are accessible.
  4. Blueos keeps restarting after seconds.