Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#110: Try to get rid of Vagrant and VirtualBox in favor of VM-ish Docker container #111

Merged
merged 8 commits into from
Mar 24, 2018

Conversation

BR0kEN-
Copy link
Owner

@BR0kEN- BR0kEN- commented Mar 17, 2018

#110

All commands must be executed within CIKit project directory, created by the init script, e.g.:

cikit init --project=test_project
cd test_project

Local environment

cikit env/start

Provsion the container

cikit provision

Login to the container

cikit ssh

Stop the container

cikit env/stop

Remove the container

cikit env/rm

Missing features in comparison to Vagrant + VirtualBox approach

  • DNS proxy server that allows accessing container's network by hostname.
  • Storing the answers to provisioner in environment.yml.

@BR0kEN-
Copy link
Owner Author

BR0kEN- commented Mar 19, 2018

Well, unfortunately, DNS proxy it's kinda huge issue for the moment...

cikit init --project=webserver --without-sources
cd webserver
cikit env/start
docker ps -a
CONTAINER ID        IMAGE                   COMMAND                  CREATED             STATUS              PORTS                                                                                             NAMES
ad6cf111fdd2        solita/ubuntu-systemd   "/bin/bash -c 'exec …"   2 days ago          Up 41 minutes       0.0.0.0:32791->80/tcp, 0.0.0.0:32790->443/tcp, 0.0.0.0:32789->3306/tcp, 0.0.0.0:32788->4444/tcp   webserver.loc
  • 0.0.0.0:32791, 0.0.0.0:32790, 0.0.0.0:32789, 0.0.0.0:32788 etc. - works as expected: request from host routes to an appropriate port within the container.
  • webserver.loc, webserver.loc:443, webserver.loc:3306, webserver.loc:4444 etc. - needs a DNS proxy implemented.

@BR0kEN- BR0kEN- force-pushed the issues/110 branch 2 times, most recently from b4231ea to 7557e21 Compare March 19, 2018 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant