Trying to aurorun my application on verdin 8mP

[sudhaa12232]

Hello Team ,
I have Verdin 8mp board.
I have verdin development board
I want to autostart my application. I am doing create-production-image. I am getting error response

• Executing task: pwsh -nop /home/stryker/cam/.conf/createDockerComposeProduction.ps1 /home/stryker/cam torizon v0.0.0 registry-1.docker.io cam -imx8

Docker registry password: ************
Rebuilding torizon/cam:v0.0.0 …

Executing task: apply-torizon-packages-arm64 <
Applying torizonPackages.json …
Applying to Dockerfile.debug …
Dockerfile.debug
Applying to Dockerfile …
Dockerfile
torizonPackages.json applied
Executing task: build-container-torizon-release-arm64 <
WARN[0000] /home/stryker/cam/docker-compose.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Building 1.9s (14/14) FINISHED docker:default
=> [cam internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.55kB 0.0s
=> [cam internal] load metadata for docker.io/torizon/debian:3.5.0 1.8s
=> [cam auth] torizon/debian:pull token for registry-1.docker.io 0.0s
=> [cam internal] load .dockerignore 0.0s
=> => transferring context: 117B 0.0s
=> [cam 1/7] FROM docker.io/torizon/debian:3.5.0@sha256:f8f8f3446231a51c7e91f1d93b0e1beb553576d01e09df53bc98298755233e7a 0.0s
=> [cam internal] load build context 0.0s
=> => transferring context: 97B 0.0s
=> CACHED [cam 2/7] RUN apt-get -q -y update && apt-get -q -y install python3-minimal python3-pip python3-venv && apt-get clean && apt-get au 0.0s
=> CACHED [cam 3/7] RUN python3 -m venv /home/torizon/app/.venv --system-site-packages 0.0s
=> CACHED [cam 4/7] COPY requirements-release.txt /requirements-release.txt 0.0s
=> CACHED [cam 5/7] RUN . /home/torizon/app/.venv/bin/activate && pip3 install --upgrade pip && pip3 install -r requirements-release.txt && rm requiremen 0.0s
=> CACHED [cam 6/7] COPY ./src /home/torizon/app/src 0.0s
=> CACHED [cam 7/7] WORKDIR /home/torizon/app 0.0s
=> [cam] exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:6d976bf960a04596c00f3b607bc0730d0e981a204e6e512d51b739768eab9d41 0.0s
=> => naming to docker.io/torizon/cam:v0.0.0 0.0s
=> [cam] resolving provenance for metadata file 0.0s
Image rebuild and tagged
Pushing it torizon/cam:v0.0.0 …
Error response from daemon: Get “https://registry-1.docker.io/v2/”: unauthorized: incorrect username or password
NativeCommandExitException: /home/stryker/cam/.conf/createDockerComposeProduction.ps1:173:1
Line |
173 | Write-Output “$psswd” | docker login $registry -u $dockerLogin --pass …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Program “docker” ended with non-zero exit code: 1.

• The terminal process “pwsh ‘-nop’, ‘/home/stryker/cam/.conf/createDockerComposeProduction.ps1’, ‘/home/stryker/cam’, ‘torizon’, ‘v0.0.0’, ‘registry-1.docker.io’, ‘cam’, ‘-imx8’” terminated with exit code: 1.
• Terminal will be reused by tasks, press any key to close it.

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

Thank you for reaching out with your question about autostarting your application on the Verdin iMX8M Plus board using Torizon. It seems like you’re encountering an issue with Docker authentication during the process.

The error message “unauthorized: incorrect username or password” suggests that there might be an issue with the Docker login credentials. Here are some steps you can take to resolve this:

1. Verify Docker Credentials: Double-check the username and password you are using for Docker Hub. You can test these credentials by manually logging in with the command docker login in your terminal.

2. Review Script Configuration: Look into the createDockerComposeProduction.ps1 script to ensure it correctly handles the Docker credentials. Make sure the variables for the username and password are set accurately.

3. Check Environment Variables: If your script relies on environment variables for credentials, confirm that these are correctly set in your environment.

4. Reset Docker Configuration: If needed, you can reset your Docker credentials by removing the ~/.docker/config.json file and then logging in again.

Once you’ve resolved the authentication issue, you can proceed with building and deploying your Docker images. Ensure that your docker-compose.yml file is correctly configured and placed in the /var/sota/storage/docker-compose/ directory to enable autostart of your containers at boot.

I hope this helps you get your application running smoothly. If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Build, Test and Push Applications for Production | Toradex Developer Center

Auto start application on boot up

Hi, I want my application to run automatically upon boot up. I followed the instructions on How to Autorun Application at the Start up in Linux | Toradex Developer Center When I tried the above resolution, I got “bad-setting (Reason: Unit .service has a bad unit file setting)” error. The post is more than 7 years old. How do I make my application to start automatically on boot up? The application is stored at /opt/Phoenix/bin/Phoenix on my target device. Hardware: Boot2Qt 6.2.1 Toradex Verdin-…

Imx8x Torizon 5.7.2 to 6.3 Upgrade Journey - permissions on /etc/docker wrong on update.

[eric.tx]

hey @sudhaa12232,

Are pulling from a private docker repository?

You will need to set this up.

DockerHub private Container Registry | Toradex Developer Center

-Eric

[michael.tx]

Hi @sudhaa12232 ,

Any update here for us?

Best,

[sudhaa12232]

Above worked for me