Opened 9 years ago
Closed 8 years ago
#47998 closed submission (wontfix)
[NEW] boot2docker
| Reported by: | ajdudman | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | pixilla (Bradley Giesbrecht), mkae (Marko Käning), petrrr, jeisch@… | |
| Port: | boot2docker |
Description
Boot2docker is a command-line interface to docker. This tool downloads the boot2docker ISO image, creates a VirtualBox virtual machine, sets up two networks for that virtual machine and then provides the user a simple way to login via SSH. This port works with the docker port in ticket #43260. Please keep the versions matched. Since the build process calls git through go -d, might as well fetch with git as well. I based this Portfile on the homebrew formula.
Attachments (1)
Change History (10)
comment:1 Changed 9 years ago by larryv (Lawrence Velázquez)
comment:2 Changed 9 years ago by ajdudman
Yes. This can be avoided by moving the "go -d" to a post-fetch procedure. When port -svd fetch is run, I see next to last:
DEBUG: Executing proc-post-org.macports.fetch-fetch-0
Is there a way for debug to expose the system call inside post-fetch?
Changed 9 years ago by ajdudman
all fetching done in fetch and post-fetch
comment:3 Changed 9 years ago by mf2k (Frank Schima)
| Keywords: | Linux container removed |
|---|---|
| Version: | 2.3.3 |
comment:7 follow-up: 8 Changed 8 years ago by neverpanic (Clemens Lang)
Is this still relevant now that we have a docker-machine port?
comment:8 Changed 8 years ago by ajdudman
comment:9 Changed 8 years ago by petrrr
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Was substituted by port docker-maschine.
Replying to ajdudman@…:
Is there a way to avoid this? We really prefer that ports not perform network activity during any phase other than the fetch phase.