-
Notifications
You must be signed in to change notification settings - Fork 4
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
Updates for 0.9.0 #43
base: master
Are you sure you want to change the base?
Conversation
I've been testing with: |
- 57774:52773 | ||
- 53773 | ||
volumes: | ||
- ~/iris.key:/usr/irissys/mgr/iris.key |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we add a comment in the README for iris.key?
iris: | ||
build: | ||
context: . | ||
dockerfile: Dockerfile-amd64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to build this image successfully but have not been able to create a container using docker run
. I think the reason lies in the hardcoded amd64
part here. We should probably get the architecture string from environment variables.
This covers the %ZPM->%IPM rename and some backwards-incompatible default behaviors around namespace segmentation to keep things as seamless as possible.
NOTE: this shouldn't go forward prior to IPM 0.9.0 release, or could work around by not having IPM_INSTALLER point to the "latest" (possibly breaking compatibility) version.