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

Provide a docker image to make it easy to try Pyston #1096

Open
kmod opened this issue Feb 10, 2016 · 7 comments
Open

Provide a docker image to make it easy to try Pyston #1096

kmod opened this issue Feb 10, 2016 · 7 comments
Labels
old_v1 Issues leftover from the old v1 series probably easy

Comments

@kmod
Copy link
Collaborator

kmod commented Feb 10, 2016

Or maybe some other tool (Vagrant was suggested at one point). This gets asked for fairly regularly and I think is appreciated in other projects when available.

We're happy to help out from the Pyston side but if anyone with some experience setting up docker containers wants to give this a go, it would really helpful :)

@corona10
Copy link

I simply made for v0.4 as sample
You can pull image by docker pull corona10/pyston:0.4
And also here is the link

@corona10
Copy link

but in my opinion we can do better job with automated build for provide latest pyston docker image

@jakirkham
Copy link

+1 for a docker image. Should be pretty easy considering this should already build on Ubuntu (version? precise?). Could just use a base image that starts with that version of Ubuntu and then apt-get anything else that is needed. Also, could use Docker Hub automated builds so dev releases can be tried easily.

@aisk
Copy link
Contributor

aisk commented Feb 17, 2016

I used Vagrant to build Pyston for a while, this is the Vagrant file I used: https://gist.github.com/aisk/efd38d84575ed7087280

I think we can provide docker and vagrant envs both to let people choose which they want (since use docker in OSX is not straight-forwar), and maintain both of them seems not a hard work.

@funkyfuture
Copy link

for what i can tell an automated build seems out of its resources limits (2h and afair 1GB RAM, 1 CPU and 30GB drive).

i suppose a debian package would be a good idea anyway. if that dependency on texlive-extra-utils with its vast amount of dependencies wouldn't be required a build may fit within the limits.

@kmod kmod added the old_v1 Issues leftover from the old v1 series label Oct 28, 2020
@kmod kmod closed this as completed Oct 28, 2020
@jakirkham
Copy link

Congrats on your new company! Glad to see this project moving forward 😄 🎉

@kmod kmod reopened this Oct 28, 2020
@kmod
Copy link
Collaborator Author

kmod commented Oct 28, 2020

Thanks @jakirkham !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
old_v1 Issues leftover from the old v1 series probably easy
Projects
None yet
Development

No branches or pull requests

5 participants