Opened 2 years ago

Closed 6 months ago

#131 closed defect (fixed)

problem with compiling

Reported by: oatiz@… Owned by: wiese
Priority: normal Component: BNC
Version: Keywords:

Description (last modified by anonymous)

When we tried to compile by running "sudo docker build -t bnc:2.13 ." command the process ends with success. But we cant see the bnc executable in /tmp/BNC/ folder.

Attachments (0)

Change History (7)

comment:1 by anonymous, 2 years ago

Description: modified (diff)

comment:2 by wiese, 2 years ago

At the end of the build, you should see the following lines:
STEP 15/15: RUN ./bnc --version
BNC 2.13.0

If not, the build was not successfully and you should see errors in the log.

comment:3 by anonymous, 2 years ago

Yes I see the same output but could not find the ./bnc executable.

comment:4 by wiese, 2 years ago

When the version is printed, the bnc binary must exist.
To see it you have to run the image: docker run -it <imageID>.

You can copy it from the container to your host with docker cp <containerID>:/tmp/BNC/bnc .

comment:5 by wiese, 2 years ago

Owner: changed from stuerze to wiese
Status: newaccepted

comment:6 by anonymous, 2 years ago

Thank you for your answer. I tried to start ./bnc but see the output below. I am running "docker run -it bnc:2.13" command at first. How can I start the software?

atak@atak-pc:~$ sudo docker run -it bnc:2.13
root@39690c7b5584:/tmp/BNC# ./bnc
qt.qpa.screen: QXcbConnection: Could not connect to display 
Could not connect to any X display.

I also copied the bnc to my home directory. But when I try the "./bnc --version" command, I see the output below.

atak@atak-pc:~$ ./bnc --version
./bnc: /usr/lib/x86_64-linux-gnu/ version `Qt_5.11' not found (required by ./bnc)

comment:7 by stuerze, 6 months ago

Resolution: fixed
Status: acceptedclosed

Modify Ticket

Change Properties
as closed The owner will remain wiese.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.