How do i fix this error while running vagrant? - docker

Received the following message:
dpkg-deb: error: 'vagrant_2.3.4_x86_64.deb' is not a Debian format archive
dpkg: error processing archive vagrant_2.3.4_x86_64.deb (--install):
dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
vagrant_2.3.4_x86_64.deb
While running the following command:
dpkg -i vagrant_$(echo $vagrant_latest_version)_x86_64.deb
I was trying to build a Virtual Machine inside my docker. (https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1). I cannot get back to the docker since i closed the whole terminal.
How could i download or fix the file missing?

Related

Docker selenium firefox image creation issue

I'm trying to create a selenium firefox node image. I've added the "COPY generate_config /opt/bin/generate_config" command to copy the generate_config file from local. Then when I run the command "RUN /opt/bin/generate_config > /opt/selenium/config.json" , I get error -
**# #10 0.320 /bin/sh: 1: /opt/bin/generate_config: not found
------**
executor failed running [/bin/sh -c /opt/bin/generate_config > /opt/selenium/config.json]: exit code: 127
Can anyone please help me with solution
I tried adding sudo, changing the cat command. nothing worked.

MongooseIM keeps throwing FATAL FIPS SELFTEST FAILURE after server restart

I am testing MongooseIM v.5.0.0 for my project.
I download the deb file for Ubuntu Xenial from this link
And I deployed it under Ubuntu 16.04 Xenial AMD in VM.
I haven't customized its config files and just simply run it. My problem is: after restarting my VM a few times, the MongooseIM doesn't want to start and throws an error like below
root#ubuntu:~# mongooseimctl foreground
Root: /usr/lib/mongooseim
Exec: /usr/lib/mongooseim/erts-12.1/bin/erlexec -noshell -noinput +Bd -boot
/usr/lib/mongooseim/releases/5.0.0/start -embedded -config /etc/mongooseim/app.config -
args_file /etc/mongooseim/vm.args -args_file /etc/mongooseim/vm.dist.args -- foreground
fips.c(139): OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE
/usr/bin/mongooseimctl: line 165: 856 Aborted
"$RUNNER_SCRIPT_DIR"/mongooseim foreground
I search for this error, but none seems to answer my problem.
Can anybody help me?

Cannot compile Open CV on Ubuntu 18.04 because of jasper.h not found

I am trying to compile Opencv on Ubuntu 18.04. I installed many dependencies packages but when I run make I get the error:
grfmt_jpeg2000.cpp:59:10: fatal error: jasper/jasper.h: No such file or directory
#include <jasper/jasper.h>
^~~~~~~~~~~~~~~~~
compilation terminated.
I had already jasper installed and installed libjasperreports-java. However the file jasper.h cannot still be found in my system. Is there any library I can install with apt install to get that file? Or am I missing any other library?
EDIT 1
I tried also downloading the opencv_contrib to install extra moduels of openCV but first of all jaspar is not present and secondly setting the build with
cmake -D CMAKE_INSTALL_PREFIX=./ -D CMAKE_BUILD_TYPE=Debug -D OPENCV_EXTRA_MODULES_PATH=../opencv_contrib/modules ../openCV
returns the error:
Make Error at cmake/OpenCVModule.cmake:352 (message):
Duplicated modules NAMES has been found
while CMakeError.log contains many errors of the type:
Build output check failed:
Regex: 'command line option .* is valid for .* but not for C\+\+'
Output line: 'cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++'

error when install tools in docker container

I install ubuntu-14.04.4-server-amd64.iso in my VirtualBox,then I use some way to get its rootfs. after that i can the rootfs to create my docker image.the Dockerfile as following:
FROM scratch
COPY rootfs /
RUN chmod u+s /usr/bin/sudo && chmod u+s /bin/mount && chmod u+s /bin/umount
I start my docker container,then I install some tools,like minicom,wget ...,but error,the following is error msg:
root#20ca319c51e6:~$ apt-get install minicom
Reading package lists... Done
Building dependency tree
Reading state information... Done
minicom is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up libpam-systemd:amd64 (204-5ubuntu20.19) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
runlevel:/var/run/utmp: No such file or directory
dpkg: error processing package libpam-systemd:amd64 (--configure):
subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
libpam-systemd:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I also try to "apt-get update;apt-get upgrade",but get same error msg too,
what's should i do.need you help! thanks all :)

Xcode Build error, arm-apple-darwin11-gcc-4.2.1 execvp: No such file or directory

After upgrading to Xcode 4.3.2. I'm getting a metric ton of build errors.
A whole line of them are error code 255
gcc-4.2: error trying to exec '/usr/bin/arm-apple-darwin11-gcc-4.2.1': execvp: No such file or directory
Command /usr/bin/gcc-4.2 failed with exit code 255
I noticed that there is no /usr/bin/arm-apple-darwin11-gcc-4.2.1 file on my machine. Could this be the source of the problem?
What's the output of this command?
$ printenv | grep "CC="
It might be honoring your C Compiler (CC) selection. I was getting similar errors (through cocoapods) and doing an
$ export CC=
fixed it for me.

Resources