Virtualbox problems with Linux
I have a problem with creating virtual machine with docker-machine and virtualbox.
When I am running
docker-machine create --driver virtualbox newvm
command, I am getting the following error .
Running pre-create checks...
Error with pre-create check: "We support Virtualbox starting with version 5. Your VirtualBox install is \"WARNING: The vboxdrv kernel module is not loaded. Either there is no module\n available for the current kernel (4.10.0-42-generic) or it failed to\n
load. Please recompile the kernel module and install it by\n\n
sudo /sbin/vboxconfig\n\n You will not be able to start VMs until this problem is fixed.\n5.2.4r119785\". Please upgrade at https://www.virtualbox.org"
I have installed latest version of virtual box which error brings, but after running command it brings the same problem.I cant find the reason of this error
How can I solve this problem ?
See also questions close to this topic
Docker run mapping ports does not work in ubuntu 16.04
I am using a Docker version 18.03.1-ce, build 9ee9f40 on ubuntu 16.04 and trying to run the command:
docker run -p 4000:5000 Repository_Name
It's not opening in a browser using
But if I run with
docker run --net host -p 4000:5000 Repository_Name
It's opening in a browser using
I want to change from Expose port say
5000to host port
4000. so that in a browser I can run it using
https://localhost:4000. Please explain how to resolve the issue.
Setting MongoDB profiling level from command line
Currently, it is possible to set the MongoDB profiling level while in the shell using 'db.setProfiling(2)'. However, is there anyway to set the profiling level as a command line argument when starting the mongod instance? For example, something to the effect of 'mongod --profiling 2'. I have MongoDB running in a Docker and need to start it using supervisord, and currently just use the command 'mongod'.
Create and fill database in docker container
I'm trying to run my own container from image, which is based on original postgres image. I want also add some configuration like db name which should be created, user and pw as you can see below, and also run init script which contains script for creating tables and some insers.
here is my dockerfile:
FROM postgres:9.5-alpine ENV POSTGRES_PASSWORD: postgres ENV POSTGRES_USER: postgres ENV POSTGRES_DB: fooDB COPY init.sql /docker-entrypoint-initdb.d/ EXPOSE 5432 CMD ["postgres"]
when I run psql in container like this:
docker exec -it <container> psql -U postgres -W postgres
and check created databses with list command
I got this output:
Why there is no my database and how to ensure to be created? Thank you for advices.
I am using that dockerfile in docker compose:
... db: build: . ports: - "5432"
Vagrant install box errors
Trying to install Vagrant on OSX Sierra. Finally got virtualbox to download manually:
box: Adding box 'hashicorp/precise64' (v1.1.0) for provider: virtualbox box: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box ==> box: Successfully added box 'hashicorp/precise64' (v1.1.0) for 'virtualbox'!
But when I try to use "vagrant up" Vagrant doesn't see it
wordpress$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'base' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: >= 0 ==> default: Box file was not detected as metadata. Adding it directly... ==> default: Adding box 'base' (v0) for provider: virtualbox default: Downloading: base An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
Couldn't open file /Users/wordpress/base
When I ask for vagrant box list I get
hashicorp/precise64 (virtualbox, 1.1.0)
so I know it's there.
in the Oracle VM VirtualBox manager, the name is set to VirtualBoxWPMachine.
I tried following the instructions listed in the other question: Virtualbox Widnows VM to Vagrant base box
when I ran
vagrant box install --base VirtualBoxWPMachine --output /hashicorp/precise64
I got that it didn't recognize "install" as an available subcommand.
How do I fix it?
SAS Studio: Using data in "myfolders"
I have established a shared folder with VM Virtualbox and uploaded a .sas7bdat data file. When I open SAS Studio to use the university edition, I can see this data file in "myfolders." However, when I try to print the contents or do anything with this data file, I constantly get errors.
Below is my current code to move this data file into my work library.
PROC IMPORT DATAFILE="/folders/myfolders/Lawrence.sas7bdat" OUT=WORK.lawrence; run;
Then, I get this error:
1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 72 73 *data Lawrence; 74 *run; 75 76 PROC IMPORT DATAFILE="/folders/myfolders/Lawrence.sas7bdat" 77 OUT=WORK.lawrence; ERROR: Unable to determine datasource type. Please use the DBMS= option.
What is the "option" to use for a .sas7bdat data file?
I just want to manipulate this data file. Thank you!
How to remove the shadow effect on windows in CentOS, for Virtualbox seamless mode?
Per the title, anyone know how to remove the window shadow effect in CentOS? I'm running CentOS as a VM in virtualbox and, in seamless mode, the shadow effect is leading to an annoying border around my windows.
Docker machine's database persists after docker-machine rm | How do I remove the db?
Whenever I break the database on my local development instance I am able to easily run 'docker-machine rm dev-instance'. This works, and I can just recreate a new docker-machine with 'docker-machine create --driver virtualbox dev'. Then just rebuild the machine with 'docker-machine -f local.yml build' and 'docker-compose -f local.yml up'. All works great with this approach on Mac OS.
However, on my Ubuntu machine, when I run 'docker-machine rm -f dev-instance' it deletes the dev instance and I think all is fine. I go through the usual process of recreating my dev instance. It builds successfully, but way too fast -- it's not creating a new machine it doesn't look like.. It seems to be caching the last docker machine. I confirm this when I run 'docker-compose -f local.yml up'. This isn't very helpful though, because I still run into the same errors I had with my DB before -- I was hoping to nuke my instance of everything and start fresh, but I can't quite get it to work on Ubuntu.
Any suggestions would be greatly appreciated, please let me know what other details would be useful to provide. Thanks in advance!
docker image prune is not working
Have tried the following commands, but none of them delete the images.
sudo docker images prune --filter "dangling=true" sudo docker images prune --all sudo docker images prune -a sudo docker images prune
Output for both the commands:
REPOSITORY TAG IMAGE ID CREATED SIZE
$ sudo docker version Client: Version: 1.12.6 API version: 1.24 Go version: go1.6.4 Git commit: 78d1802 Built: Tue Jan 10 20:26:30 2017 OS/Arch: linux/amd64 Server: Version: 1.12.6 API version: 1.24 Go version: go1.6.4 Git commit: 78d1802 Built: Tue Jan 10 20:26:30 2017 OS/Arch: linux/amd64
Docker doc suggests this command, but I encountered error
$ sudo docker image prune -a docker: 'image' is not a docker command. See 'docker --help'.`
"docker-machine create" gives connection attempt failed error when run from behind a corporate proxy
I am new to docker and am trying to create a docker host using the
docker-machine create [name]command on Windows 7 but I always get a connection attempt failed error. I added the
Docker Toolbox\start.shbut that did not help
Also tried :
--engine-env HTTP_PROXY=http://proxy IP:portCLI option for docker-machine create command
- Windows powershell command
$env:HTTP_PROXY=http://proxy IP:portto set the environment variable at global level
But none of these have resolved the issue.
docker-machine version and the error:
docker-machine.exe version 0.14.0, build 89b8332
docker-machine create node-1
(node-1) Unable to get the latest Boot2Docker ISO release version: Get https://api.github.com/repos/boot2docker/boot2docker/releases/latest: dial tcp 22.214.171.124:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.