I am trying to create a python project on IVY, but VSCode just seems to build it locally

Technical Support
, , ,
1

I’ve tried several times to setup a python project in VSC, using the template, while connected to my IVY plus board with an IMX8MP module. For some reason, itn the launch.json, it has “Pyton Local”, “Torizon arm32” and “Torizon arm64”, but I can only get it to run Python local, i.e. my computer WSL. My device is connected and set as default.
I reset the system and built again, and set my device as default (again). But this time when I went to debug, I saw a dropdown box show up at the top that said “Local”, then clicked on it and I found the Torizon arm64 l was looking for.
However, after it finallly built the docker, it came up with an error. But when I clicked on the dialog box button that said show errors, it said there weren’t any.
The error shown was: prelaunch Task ‘deploy-torizon-arm64’ terminated with exit code 18.

What is that error mean?

Thanks,
Steve

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello Steve,

Thank you for your detailed explanation. The error code 18 in the context of the prelaunch task deploy-torizon-arm64 typically indicates a problem with transferring files to your device’s debug container over SSH. This can be caused by several issues related to connection, configuration, or permissions. Here’s how you can systematically troubleshoot this:

1. Check Device Connection Settings

Ensure that your device connection details (IP address, username, etc.) are correct in .vscode/settings.json. A mismatch or typo here will prevent successful deployment.

Reference:
Workspace files and files inside containers

2. Confirm SSH Credentials

Make sure your SSH key or password is properly configured and that the Toradex device can be accessed via SSH from your development PC. Try manually connecting via SSH to validate connectivity.

3. Validate File Locations (Especially with WSL)

If your project files are on a Windows filesystem (e.g., /mnt/c/), it is recommended to move them to your Linux filesystem (e.g., ~/) when using WSL. Accessing files from the Windows side can cause permission and performance issues:

“If you’re running VS Code under WSL, make sure your project workspace is located in the Linux filesystem and not on the Windows mounted filesystem.”
More info here

4. Debug Container Configuration

  • For Python projects, ensure your requirements-debug.txt lists all needed dependencies.
  • Your Dockerfile.debug should be properly set up to build the debug container environment.

Reference:
Adding dependencies and tools to existing project

5. Additional Checks

  • Make sure no firewall or network rules block SSH (port 22) or interfere with the connection.
  • If you have previously connected to other Toradex boards, deleting and re-adding the device in the Toradex Devices extension can sometimes resolve mismatched configuration.

Summary of Recommendations:

  • Double-check your SSH credentials and device address in .vscode/settings.json.
  • Move your project to your Linux home directory (if using WSL).
  • Ensure the debug Dockerfile and requirements files are correct.
  • Try to SSH to your device manually and resolve any access/permission errors.
  • If the device was previously added with different settings, re-add it in the VS Code extension.

Let me know if you need step-by-step instructions for any of these checks or run into specific issues when trying them!

Best regards,
Toradex AI Assistant.

3

Hey @EvetsMostel1,

Can you post the full output logs that include this error?

4

@eric.tx
I changed some things as it also kept putting my ip address of my desktop on a ethernet port that wasn’t correct, but now I am getting this:
Error response from daemon: Get “https://192.168.5.10:5002/v2/”: http: server gave HTTP response to HTTPS client
I remember seeing this error with other previous setups using C++, but don’t remember how I solved it.

[05-13 10:56:29.259] Activating Torizon IDE …

[05-13 10:56:29.260] Torizon IDE version :: 3.0.4

[05-13 10:56:30.320] Latest Torizon IDE published :: 3.0.110

[05-13 10:56:30.320] Telemetry is enabled

[05-13 10:56:30.320] Extension collects completely anonymous telemetry data about templates usage. Participation in this anonymous program is optional, and you may opt-out if you’d not like to share any information. Check: Settings - Data Collection | Toradex Developer Center

[05-13 10:56:30.320] Telemetry allows us to accurately gauge templates usage. This data will help us to focus better on the most used templates, adding new features and putting effort in the right place.

[05-13 10:56:30.321] Resolving host IP address …

[05-13 10:56:33.785] Host IP address OK

[05-13 10:56:33.794] Docker installed OK

[05-13 10:56:34.259] Docker running OK

[05-13 10:56:34.671] Docker compose OK

[05-13 10:56:34.682] PowerShell OK

[05-13 10:56:33.989] git OK

[05-13 10:56:33.998] dig OK

[05-13 10:56:34.05] avahi-resolve OK

[05-13 10:56:34.013] nmap OK

[05-13 10:56:34.020] iputils-ping OK

[05-13 10:56:34.030] file OK

[05-13 10:56:34.039] sshpass OK

[05-13 10:56:34.050] iproute2 OK

[05-13 10:56:34.058] rsync OK

[05-13 10:56:34.064] python3 OK

[05-13 10:56:34.069] pipx OK

[05-13 10:56:34.071] Cloning project templates

[05-13 10:56:34.071] Templates repo: GitHub - torizon/vscode-torizon-templates: VS Code Torizon Integrated Development Environment Templates

[05-13 10:56:34.071] Templates tag/hash: v3.0.4

[05-13 10:56:34.084] Project templates clone of branch OK

[05-13 10:56:34.930] Project templates fetched OK

[05-13 10:56:34.948] Checkout templates repo to tag v3.0.4 OK

[05-13 10:56:37.145] xonsh installation OK

[05-13 10:56:37.146] Checking connected devices …

[05-13 10:56:37.146] Scanning Torizon devices …

[05-13 10:56:37.156] Debian bookworm packages list load OK

[05-13 10:56:37.156] Debug id_rsa OK

[05-13 10:56:37.246] Checking host ip sanity …

[05-13 10:56:39.422] Torizon IDE extension activated

[05-13 10:56:39.476] Host ip is OK

[05-13 10:56:39.535] Device 192.168.5.38 set as Docker Host

[05-13 10:59:34.465] ERROR :: pull-container-torizon-debug-arm64 failed with exit code 18

[05-13 11:04:53.580] ERROR :: pull-container-torizon-debug-arm64 failed with exit code 18

[05-13 11:37:13.013] ERROR :: pull-container-torizon-debug-arm64 failed with exit code 18

[05-13 11:39:32.186] ERROR :: pull-container-torizon-debug-arm64 failed with exit code 18
Steve

5

OK, I fixed this problem, but now having another. The solution was add:
“insecure-registries” : [“192.168.5.10:5002”]
to /etc/docker/daemon.json and to restart my device (again). Not sure why it didn’t take the first time.
But now I have another problem. I am just running a modified "Hello Torizon! python script and if i just run it, it works fine. But if I put in a breakpoint at an if statement, it stops there, but then the active line comes and goes. If I hit F5 again, it tries to start everything over, like the debugger has exited instead of continuing on. and it errors out because of a “broken pipe”. Here’s my program, the → shows where I put my breakpoint:
#!python3

if name == “main”:
print(“Hello Torizon!”)

for i in range(1000):
print(i)
→ if i == 999:
print(“Done!”)
break
else:
continue
print(“This will never be printed”)

This works fine when I run it locally including the breakpoint. But even without the breakpoint, it only outputs to 477 before it exits.

Evets

6

Hey @EvetsMostel1,

Are you able to share the logs produced from this behavior?

-Eric

7

Hi @eric.tx ,
Today, I can’t even run it, it fails on deployment. I can run it on my PC. Here are the logs:
_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose -p torizon up -d anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Building 0.0s (0/0) docker:default
WARN[0000] Found orphan containers ([torizon-pantilt-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 1/1
:heavy_check_mark: Container torizon-anaheimpy3-debug-1 Started 0.1s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 pkill python3 || true

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: rsync -P -av -e ssh -p 6502 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null /home/steve/AnaheimTestC/src torizon@192.168.5.38:/home/torizon/app/

ssh: connect to host 192.168.5.38 port 6502: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(232) [sender=3.2.7]

  • The terminal process “rsync ‘-P’, ‘-av’, ‘-e’, ‘ssh -p 6502 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null’, ‘/home/steve/AnaheimTestC/src’, ‘torizon@192.168.5.38:/home/torizon/app/’” failed to launch (exit code: 255).

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: xonsh .conf/validate-deps-running.xsh

:warning: VALIDATING ENVIRONMENT

OS: Linux
OS Version: 5.15.167.4-microsoft-standard-WSL2
OS Arch: x86_64
Under WSL: Ubuntu-22.04
VS Code:
1.100.2
848b80aeb52026648a8ff9f7c45a9b0a80641e2e
x64

TOR Extension: toradex.apollox-vscode@3.0.4

:white_check_mark: Environment is valid!

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: bash -c [[ ! -z “192.168.5.38” ]] && true || false

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: bash -c [[ “aarch64” == “aarch64” ]] && true || false

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: sleep 1

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: sshpass -p torizon1 scp -P 22 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no /home/steve/AnaheimTestC/docker-compose.yml torizon@192.168.5.38:~/

Warning: Permanently added ‘192.168.5.38’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 docker image prune -f --filter=dangling=true

Total reclaimed space: 0B

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: docker compose -p torizon stop anaheimpy3 anaheimpy3-debug && docker compose -p torizon rm -f anaheimpy3 anaheimpy3-debug

No stopped containers

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: xonsh /home/steve/AnaheimTestC/.conf/torizon-packages.xsh arm64

Applying torizonPackages.json:
Applying to Dockerfile.debug …
:white_check_mark: Dockerfile.debug
Applying to Dockerfile …
:white_check_mark: Dockerfile
torizonPackages.json applied

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST= docker compose build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm64 --build-arg DEBUG_SSH_PORT=6502 --build-arg GPU=-imx8 anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Building 0.8s (13/13) FINISHED docker:default
=> [anaheimpy3-debug internal] load .dockerignore 0.0s
=> => transferring context: 117B 0.0s
=> [anaheimpy3-debug internal] load build definition from Dockerfile.debug 0.0s
=> => transferring dockerfile: 2.82kB 0.0s
=> [anaheimpy3-debug internal] load metadata for docker.io/torizon/debian:4 0.7s
=> [anaheimpy3-debug 1/8] FROM docker.io/torizon/debian:4@sha256:cca23c84946621ee72aae4593da5f3 0.0s
=> [anaheimpy3-debug internal] load build context 0.0s
=> => transferring context: 43B 0.0s
=> CACHED [anaheimpy3-debug 2/8] RUN apt-get -q -y update && apt-get -q -y install open 0.0s
=> CACHED [anaheimpy3-debug 3/8] RUN apt-get -q -y update && apt-get -q -y install && 0.0s
=> CACHED [anaheimpy3-debug 4/8] RUN python3 -m venv /home/torizon/app/.venv --system-site-pack 0.0s
=> CACHED [anaheimpy3-debug 5/8] COPY requirements-debug.txt /requirements-debug.txt 0.0s
=> CACHED [anaheimpy3-debug 6/8] RUN . /home/torizon/app/.venv/bin/activate && pip3 install 0.0s
=> CACHED [anaheimpy3-debug 7/8] RUN mkdir /var/run/sshd && sed 's@session\srequired\spam 0.0s
=> CACHED [anaheimpy3-debug 8/8] RUN rm -r /etc/ssh/ssh*key && dpkg-reconfigure openssh-ser 0.0s
=> [anaheimpy3-debug] exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c93dd1023a9a06a95bc0cc3d20ef14cf9767880fa4e3e70c7677a2474a6d1763 0.0s
=> => naming to localhost:5002/anaheimpy3-debug:arm64 0.0s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST= docker compose push anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Pushing 0/0
⠋ Pushing anaheimpy3-debug: b3efd35b11af Preparing 0.0s
⠋ Pushing anaheimpy3-debug: bb392264e246 Preparing 0.0s
⠋ Pushing anaheimpy3-debug: b3e30e48f4d4 Preparing 0.0s
⠋ Pushing anaheimpy3-debug: df12f399b33f Preparing 0.0s
⠋ Pushing anaheimpy3-debug: 7aa28b0b0d5d Preparing 0.0s
⠋ Pushing anaheimpy3-debug: ebaa2b1109f3 Waiting 0.0s
⠋ Pushing anaheimpy3-debug: 327c58d2f5e5 Waiting 0.0s
⠋ Pushing anaheimpy3-debug: ef5ab135b4e1 Waiting 0.0s
[+] Pushing 0/19impy3-debug: 0d44ca85e203 Waiting 0.0s
⠋ Pushing anaheimpy3-debug: b3efd35b11af Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: bb392264e246 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: b3e30e48f4d4 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: df12f399b33f Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 7aa28b0b0d5d Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ebaa2b1109f3 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 327c58d2f5e5 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ef5ab135b4e1 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 0d44ca85e203 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: cbfca7efdd64 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: c5852bef3e08 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 6cd757f87b26 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 84f02289282b Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: db9633f880e7 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ab925bd8dc65 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 5f70bf18a086 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ac6442dc9f87 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 169ce75e923c Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 66a307619b8c Layer already exists 0.0s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 LOCAL_REGISTRY=192.168.5.10 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Pulling 1/1
:heavy_check_mark: anaheimpy3-debug Pulled 0.3s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 LOCAL_REGISTRY=192.168.5.10 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose -p torizon up -d anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Building 0.0s (0/0) docker:default
WARN[0000] Found orphan containers ([torizon-pantilt-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 1/1
:heavy_check_mark: Container torizon-anaheimpy3-debug-1 Started 0.1s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 pkill python3 || true

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: rsync -P -av -e ssh -p 6502 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null /home/steve/AnaheimTestC/src torizon@192.168.5.38:/home/torizon/app/

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.
sending incremental file list
src/
src/main.py
268 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/2)

sent 412 bytes received 39 bytes 902.00 bytes/sec
total size is 268 speedup is 0.59

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 cd /home/torizon/app && . /home/torizon/app/.venv/bin/activate && screen -d -m python3 -m debugpy --listen 0.0.0.0:6512 --log-to src/log --wait-for-client src/main.py

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 ‘cT=0; while ! grep -r “: wait_for_client()” /home/torizon/app/src/log/debugpy.server*.log 2> /dev/null; do sleep 0.1; if [ “$cT” -eq 100 ]; then echo “Problem debugging main.py file”; break; fi; cT=$(expr $cT + 1); done’

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.
D+00000.626: wait_for_client()

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: xonsh .conf/validate-deps-running.xsh

:warning: VALIDATING ENVIRONMENT

OS: Linux
OS Version: 5.15.167.4-microsoft-standard-WSL2
OS Arch: x86_64
Under WSL: Ubuntu-22.04
VS Code:
1.100.2
848b80aeb52026648a8ff9f7c45a9b0a80641e2e
x64

TOR Extension: toradex.apollox-vscode@3.0.4

:white_check_mark: Environment is valid!

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: bash -c [[ ! -z “192.168.5.38” ]] && true || false

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: bash -c [[ “aarch64” == “aarch64” ]] && true || false

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: sleep 1

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: sshpass -p torizon1 scp -P 22 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no /home/steve/AnaheimTestC/docker-compose.yml torizon@192.168.5.38:~/

Warning: Permanently added ‘192.168.5.38’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 docker image prune -f --filter=dangling=true

Total reclaimed space: 0B

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: docker compose -p torizon stop anaheimpy3 anaheimpy3-debug && docker compose -p torizon rm -f anaheimpy3 anaheimpy3-debug

No stopped containers

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: xonsh /home/steve/AnaheimTestC/.conf/torizon-packages.xsh arm64

Applying torizonPackages.json:
Applying to Dockerfile.debug …
:white_check_mark: Dockerfile.debug
Applying to Dockerfile …
:white_check_mark: Dockerfile
torizonPackages.json applied

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST= docker compose build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm64 --build-arg DEBUG_SSH_PORT=6502 --build-arg GPU=-imx8 anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Building 1.2s (14/14) FINISHED docker:default
=> [anaheimpy3-debug internal] load .dockerignore 0.0s
=> => transferring context: 117B 0.0s
=> [anaheimpy3-debug internal] load build definition from Dockerfile.debug 0.0s
=> => transferring dockerfile: 2.82kB 0.0s
=> [anaheimpy3-debug internal] load metadata for docker.io/torizon/debian:4 1.2s
=> [anaheimpy3-debug auth] torizon/debian:pull token for registry-1.docker.io 0.0s
=> [anaheimpy3-debug 1/8] FROM docker.io/torizon/debian:4@sha256:cca23c84946621ee72aae4593da5f3 0.0s
=> [anaheimpy3-debug internal] load build context 0.0s
=> => transferring context: 43B 0.0s
=> CACHED [anaheimpy3-debug 2/8] RUN apt-get -q -y update && apt-get -q -y install open 0.0s
=> CACHED [anaheimpy3-debug 3/8] RUN apt-get -q -y update && apt-get -q -y install && 0.0s
=> CACHED [anaheimpy3-debug 4/8] RUN python3 -m venv /home/torizon/app/.venv --system-site-pack 0.0s
=> CACHED [anaheimpy3-debug 5/8] COPY requirements-debug.txt /requirements-debug.txt 0.0s
=> CACHED [anaheimpy3-debug 6/8] RUN . /home/torizon/app/.venv/bin/activate && pip3 install 0.0s
=> CACHED [anaheimpy3-debug 7/8] RUN mkdir /var/run/sshd && sed 's@session\srequired\spam 0.0s
=> CACHED [anaheimpy3-debug 8/8] RUN rm -r /etc/ssh/ssh*key && dpkg-reconfigure openssh-ser 0.0s
=> [anaheimpy3-debug] exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c93dd1023a9a06a95bc0cc3d20ef14cf9767880fa4e3e70c7677a2474a6d1763 0.0s
=> => naming to localhost:5002/anaheimpy3-debug:arm64 0.0s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST= docker compose push anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Pushing 0/0
⠋ Pushing anaheimpy3-debug: b3efd35b11af Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: bb392264e246 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: b3e30e48f4d4 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: df12f399b33f Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 7aa28b0b0d5d Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ebaa2b1109f3 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 327c58d2f5e5 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ef5ab135b4e1 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 0d44ca85e203 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: cbfca7efdd64 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: c5852bef3e08 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 6cd757f87b26 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 84f02289282b Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: db9633f880e7 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ab925bd8dc65 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 5f70bf18a086 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: ac6442dc9f87 Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 169ce75e923c Layer already exists 0.0s
⠋ Pushing anaheimpy3-debug: 66a307619b8c Layer already exists 0.0s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 LOCAL_REGISTRY=192.168.5.10 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Pulling 1/1
:heavy_check_mark: anaheimpy3-debug Pulled 0.3s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: DOCKER_HOST=192.168.5.38:2375 LOCAL_REGISTRY=192.168.5.10 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose -p torizon up -d anaheimpy3-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Building 0.0s (0/0) docker:default
WARN[0000] Found orphan containers ([torizon-pantilt-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 1/1
:heavy_check_mark: Container torizon-anaheimpy3-debug-1 Started 0.1s

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 pkill python3 || true

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: rsync -P -av -e ssh -p 6502 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null /home/steve/AnaheimTestC/src torizon@192.168.5.38:/home/torizon/app/

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.
sending incremental file list
src/
src/main.py
268 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/2)

sent 412 bytes received 39 bytes 300.67 bytes/sec
total size is 268 speedup is 0.59

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 cd /home/torizon/app && . /home/torizon/app/.venv/bin/activate && screen -d -m python3 -m debugpy --listen 0.0.0.0:6512 --log-to src/log --wait-for-client src/main.py

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.

  • Terminal will be reused by tasks, press any key to close it.

  • Executing task: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 6502 torizon@192.168.5.38 ‘cT=0; while ! grep -r “: wait_for_client()” /home/torizon/app/src/log/debugpy.server*.log 2> /dev/null; do sleep 0.1; if [ “$cT” -eq 100 ]; then echo “Problem debugging main.py file”; break; fi; cT=$(expr $cT + 1); done’

Warning: Permanently added ‘[192.168.5.38]:6502’ (ED25519) to the list of known hosts.
D+00000.628: wait_for_client()

  • Terminal will be reused by tasks, press any key to close it.

Steve

8

@eric.tx
Over by the call stack, I am seeing an error that says “no such file or directory. '/usr/lib/python311.zip”, briefly, just before it stops. This was not there when I ran it before. I tried recreating the environment and I get the same error. Something has changed, between now and the last time I ran this.