Docker Image #633
Replies: 4 comments 11 replies
-
Hey @leoafarias , from my point of view, we can easily satisfy both of your requirements.
It's okay to have a :latest version, but it is also important to have different images pointing to a specific version, this could be easily achieved by tagging a specific image version every time you release a new fvm version.
We can create a Dockerfile that prepares the base environment and then runs the script you created. The only thing that comes to my mind that should be implemented (if it's not already there) is the non-interactivity of the script itself. Apart from that, we can ship a docker image with a specific fvm version compiled using the new script |
Beta Was this translation helpful? Give feedback.
-
I think that some requirements would be:
|
Beta Was this translation helpful? Give feedback.
-
I also think a Docker image that is published with each fvm version at Dockerhub makes sense then customized Docker images like mine that requires a SQLite instance could use the fvm as base image. @leoafarias What are the requirements for the script to run? Does Dart need to be installed? ... |
Beta Was this translation helpful? Give feedback.
-
@leoafarias currently the pipelines generate images on each version right? I see a new docker image version here https://hub.docker.com/r/leoafarias/fvm/tags |
Beta Was this translation helpful? Give feedback.
-
There are a few open issues about Docker images in FVM, and I wanted to consolidate them in a discussion. But it's important to align a few things.
dart pub global
which is neither ideal nor version specific.It would be good to discuss the requirement for this image and if anyone can help get a PR for this. cc @deandreamatias @AngeloAvv @SebastianKlaiber
Beta Was this translation helpful? Give feedback.
All reactions