Skip to content
This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373

Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom
hheimbuerger:add-virtualbox5-support
Closed

Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom
hheimbuerger:add-virtualbox5-support

Conversation

@hheimbuerger

@hheimbuergerhheimbuerger commented Jul 12, 2015

Copy link
Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.

There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.
But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).

I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.

PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.

@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger changed the title Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger

hheimbuerger commented Jul 12, 2015

Copy link
Copy Markdown
Author

Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.

It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.

For now, I'm just taking care of these issues manually with the VBox GUI.

jmorganca
jmorganca reviewed Jul 13, 2015
View reviewed changes
Comment threadvirtualbox/machine.go

@jmorgancajmorgancaJul 13, 2015

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?

@hheimbuergerhheimbuergerJul 13, 2015

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.

@jmorganca

jmorganca commented Jul 13, 2015

Copy link
Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!

  • See GH comments
  • Squash commits and sign it off see this

I've added some notes.

@hheimbuerger

hheimbuerger commented Jul 13, 2015

Copy link
Copy Markdown
Author

Did it also create a VM with the maximum available CPUs and huge memory requirements for you?

@hheimbuerger

hheimbuerger commented Jul 13, 2015

Copy link
Copy Markdown
Author

Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.

An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger

hheimbuerger commented Jul 13, 2015

Copy link
Copy Markdown
Author

It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:

sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and

Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and

[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger

hheimbuerger commented Jul 13, 2015

Copy link
Copy Markdown
Author

The cause of my connection problems was local routes and is now fixed.

The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).

@jmorganca

jmorganca commented Jul 13, 2015

Copy link
Copy Markdown

I'll give it another go to try - sorry for the delay!

@hheimbuerger

hheimbuerger commented Jul 14, 2015

Copy link
Copy Markdown
Author

Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015
Closed
Closed
@nathanleclairenathanleclaire mentioned this pull request Jul 14, 2015
Merged
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
Add VirtualBox 5 support by hheimbuerger · Pull Request #373 · boot2docker/boot2docker-cli · GitHub
Skip to content

This repository was archived by the owner on Feb 27, 2018. It is now read-only.

Add VirtualBox 5 support - #373
Closed
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Closed
Add VirtualBox 5 support#373
hheimbuerger wants to merge 3 commits into
boot2docker:masterfrom 
hheimbuerger:add-virtualbox5-support
Conversation
@hheimbuerger
@hheimbuergerhheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Some improvements to make boot2docker more compatible with VirtualBox 5.
There's still some issues, e.g. that you have to create the exact expected host-only network yourself to make boot2docker-cli pick it up without issues.

But at least this allowed me to bootstrap a boot2docker VM on Windows 10 with VirtualBox 5 (VBox4 doesn't work very well on Windows 10, specifically no host-only networks).
I don't think this a PR ready for merging right away. I've never wrote any go before and didn't set up a proper dev environment either. I just did the minimum steps to get a boot2docker VM up and running. But I figured I might still submit this, maybe there's something useful for you in here.
PS: I know you consider boot2docker-cli deprecated, but docker-machine has the same issues with VirtualBox 5 and its dev environment requires to have docker already running, which was a hen and egg problem for me.
@hheimbuerger
Removed --synthcpu flag on vboxmanage modifyvm because it no longer e…
b983c3e
…xists in VirtualBox 5.
@hheimbuerger
Changed the NAT port forwarding commands from controlvm to modifyvm, …
1354fff
…because the former is only valid against a running VM.
I'm not sure how/whether this ever worked, maybe controlvm was valid on stopped VMs in VirtualBox 4.x or something else happened to start the VM in between (which I doubt, because then "boot2docker init" vs. "boot2docker up" doesn't make sense anymore).
@hheimbuerger
Added print statements to the host-only network finder, because we ne…
29c9bff
…ed to have created exactly this host-only network with the VBox GUI before running init.
@hheimbuergerhheimbuerger
changed the title
Add virtualbox5 supportAdd VirtualBox 5 supportJul 12, 2015
@hheimbuerger
hheimbuerger
commented
Jul 12, 2015

Copy link


Copy Markdown

Author
Note that the VM this currently creates has 8 CPUs and 2048 MiB base memory, both of which are probably a bit excessive.
It also only allocates 8 MiB of video memory, while VirtualBox complains that it needs at least 12.
For now, I'm just taking care of these issues manually with the VBox GUI.
jmorganca
jmorganca
reviewed
Jul 13, 2015
 View reviewed changes

Comment threadvirtualbox/machine.go
@jmorgancajmorgancaJul 13, 2015

Copy link


Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove before merging?
@hheimbuergerhheimbuergerJul 13, 2015

Copy link


Copy Markdown

Author
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, probably a good idea.
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

This fixed VBox 5 issues for me. Thanks for this PR!
  • See GH comments
  • Squash commits and sign it off see this
I've added some notes.
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Did it also create a VM with the maximum available CPUs and huge memory requirements for you?
@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
Something's not right yet. I regularly have VMs which error out during boot (so I have to recreate them with boot2docker-cli) and right now, I can't manage to have the docker client connect into a fresh VM anymore.
An error occurred trying to connect: Get https://192.168.59.104:2376/v1.19/containers/json: dial tcp 192.168.59.104:2376: ConnectEx tcp: 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.

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
It stopped mounting the user directory as a shared folder (even though there's no error and it's not aborting when running boot2docker-cli). I suspect that's part of the problem. I'm getting lots of errors during boot now, for example:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault

and
Calling ioctl() to re-read partition table
partprobe: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory

and
[[1;32mSetting hostname to [[1;35mboot2docker[[0;39m [[1;32mDone.[[0;39m
mv: can't rename '/usr/local/etc/ssh/ssh_config.example': No such file or directory
mv: can't rename '/usr/local/etc/ssh/sshd_config.example': No such file or directory
grep: /usr/local/etc/ssh/sshd_config: No such file or directory

@hheimbuerger
hheimbuerger
commented
Jul 13, 2015

Copy link


Copy Markdown

Author
The cause of my connection problems was local routes and is now fixed.
The above errors (including the segfault) do still occur in the boot2docker VM. Not sure if that's VBox5-specific or if they are normal to occur in 1.7.0 (but segfaulting always feels wrong).
@jmorganca
jmorganca
commented
Jul 13, 2015

Copy link


Copy Markdown

I'll give it another go to try - sorry for the delay!
@hheimbuerger
hheimbuerger
commented
Jul 14, 2015

Copy link


Copy Markdown

Author
Now I'm having my shared folders syncing incompletely (symptom: a simple text file opens fine with vi inside the boot2docker VM, but the last 20 characters are missing when reading the same file with cat), so this is definitely not ready for primetime yet.

This was referenced Jul 14, 2015

Closed


Closed

@nathanleclairenathanleclaire
mentioned this pull request
Jul 14, 2015
 Merged

Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.


Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

4 participants

@hheimbuerger@jmorganca@SvenDowideit@tianon