search

DockStation / dockstation

DockStation is developer-centric application to managing projects based on Docker. Instead of lots of CLI commands you can monitor, configure, and manage services and containers using just a GUI.
https://dockstation.io/
2.15k stars 107 forks source link

Unable to pick another tag than latest #142

Open robertmiles3 opened 6 years ago

robertmiles3 commented 6 years ago

I have a local image sjvassoc/smart that has latest and develop tags. However, in DockStation it only shows latest and not develop. How can I get this to show all tags?

image

igor-lemon commented 6 years ago

We get versions from the Docker Registry. For local images we can't get the tags. If you'll publish your image this is work. I think we can add a possibility for working with local images too.

robertmiles3 commented 6 years ago

We'll, the image on the hub is private which is also not supported in DockStation. So, it seems I'm stuck without an option.

Is this project still going? There hasn't been a release in a while so I was just wondering. On Oct 4, 2018, 10:35 AM -0400, Igor Kozlovsky notifications@github.com, wrote:

We get versions from the Docker Registry. For local images we can't get the tags. If you'll publish your image this is work. I think we can add a possibility for working with local images too. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

igor-lemon commented 6 years ago

Yep, private and external registries don't support too.

Yes, we're working on the project but development is very very slow because we can't find money and work fulltime on this project. We're working few hours per week after general work.

robertmiles3 commented 6 years ago

Understandable. Is there an ETA for a new version that might include either of these? (looking at local registry or private remotes)

igor-lemon commented 6 years ago

So, make an estimate is very difficult right now but I hope we'll release it in v1.6 in December, because v1.5 is on final stage and we don't want to drag out 1.5 release.