Ticket search results

codesys ide docker image

orby — Fri, 12 May 2023 06:50:13 -0000

Hello, guys. Can anyone share a ready-made image codesis ide? I can't build dockerfile.

Error while building project

vcbz — Thu, 11 Aug 2022 08:53:28 -0000

I am using the docker image for codesys-ide and I am trying to start with a simple task by building a project. I have created the project in a Windows Machine with Codesys v3.5 SP16. When I run the docker image with codesys and run the following script: ~~~ # encoding:utf-8 from __future__ import print_function import os import scriptengine # opens project proj = projects.open(r"MyProject.projectarchive", primary = True) application = proj.active_application #This line causes the error application.generate_code() proj.close() ~~~ I get the following error: Error: Running script 'z:/builds/codesys_test/run.py' caused exception System.ArgumentException: Traceback (most recent call last): File "z:/builds/codesys_test/run.py", line 25, in ValueError: ScriptObjects need a non-empty Guid! Attached you will find the Project I created. The project is archived as when I tried to first open the project without archiving the libraries, Codesys complained that it couldnt find the libraries. In addition I modified the codesys bash file as I need to run my own scripts from a different folder in the docker container: ~~~ #!/bin/bash WINE=wine set -x # get first CODESYS profile and start the script with it profile=$(basename "$(ls -1 ~/.wine.cds/drive_c/CODESYS/CODESYS/Profiles/*.profile* | head -n 1 | sed 's,\.profile.*,,')") echo ${profile} # check if file exists, before we call CODESYS with it if [ ! -f ${1}.py ]; then echo "error: script '${1}.py' not found." exit -1 fi export DISPLAY=:91 Xvfb :91 &> /dev/zero & sleep 1 export WINEPREFIX=~/.wine.cds # test that running scripts work ${WINE} ~/.wine.cds/drive_c/CODESYS/CODESYS/Common/CODESYS.exe --culture=en --profile="'"${profile}"'" --runscript="z:${BASEPATH}/noop.py" --noUI 2> /dev/zero # remove output log [ -f .codesys.output.txt ] && rm -f .codesys.output.txt ${WINE} ~/.wine.cds/drive_c/CODESYS/CODESYS/Common/CODESYS.exe --culture=en --profile="'"${profile}"'" --runscript="z:${1}.py" --noUI sleep 1 killall Xvfb rm -rf /tmp/.X91* ~~~ If you have any idea of why this error happens or any suggestion on what could be the reason I would gladly appreciate it. Thanks in advanced, Victor

CODESYS V3.5.16.0 not working

Ingo — Tue, 12 May 2020 12:36:58 -0000

Currently the method in install2.sh, which is in fact doing a portable installation of the system by extracting all relevant files is not working. I didn't test install.sh, yet, but I expect even more problems with this method, as the installer is always a bit instable. The effects: ~~~ wineuser@14ff3e064512:/$ codesys ide Could not load wine-gecko. HTML rendering will be disabled. wine: configuration in '/home/wineuser/.wine.cds' has been updated. winevdm: Cannot start DOS application C:\CODESYS\CODESYS\Common\CODESYS.exe because the DOS memory range is unavailable. You should install DOSBox. winevdm: Cannot start DOS application C:\CODESYS\CODESYS\Common\CODESYS.exe because the DOS memory range is unavailable. You should install DOSBox. ~~~ ~~~ wineuser@14ff3e064512:/$ codesys export-documentation ~~~ So in fact I don't get any output on the commandline, and the commands return immediately. I guess, that this needs more investigation outside of the containers.

Windows license required

i-campbell — Tue, 12 May 2020 22:04:32 -0000

The current install script downloads and runs some windows components (eg vcrun, dotnet). If you read the license during install, it says that you can only use those components if you have a valid windows OS license. Currently those installers can be seen here: https://forge.codesys.com/tol/codesys-4-linux/docker/ci/master/tree/codesys-xinetd/install.sh#l144 So I think this ticket has three parts: 1. Document in the wiki (elsewhere?) that the installer is responsible for making sure they have a license to run the prerequisites. This may mean they need a windows OS license valid for using those components. 2. Ensure own compliance with license requirements where CODESYS 4 Linux is used. 3. Remove the dependency on vcrun and dotnet framework, to at least allow it to be run with dotnet mono. It is appreciated that point 3 is a long term goal or aspiration. It likely also requires changes in the upstream package (CODESYS IDE).

Installer doesn't work on current debian

Ingo — Sat, 14 Dec 2019 06:53:05 -0000

I tested it with the CODESYS setup of V3.5 SP15, as this worked before. Didn't check if the docker images can still be built.