Core: raspberrypi3-homeassistant docker image doesn't conform to new tagging convention

[orbsmiv]

Home Assistant release with the issue:

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Since the updated release schedule was announced on 24 March the primary home-assistant Docker image follows the new convention, including dev, rc in addition to latest builds. The raspberrypi3-homeassistant doesn't follow this convention and as of 0.66.0.beta0 there is also no latest build available.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

N/A

Traceback (if applicable):

N/A

Additional information:
N/A

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[benliles]

The latest tag is being applied to the most recent build, not the most recent release. The dev and rc tags are still missing.

[orbsmiv]

As per @benliles's comment, the tagging for the homeassistant/raspberrypi3-homeassistant image still doesn't follow that of homeassistant/home-assistant. The Home Assistant Docker Installation page (here) is now slightly more up-to-date in that it mentions (albeit incorrectly!) that there's no latest tag for the RPi3 image.

Curiously there's now also a landingpage tag, although I'm not sure what this is for. Another issue is that there's no acknowledgement of the RPi image's Dockerfile source or the build method

[ejel]

Would love to see this fixed as well.

[schwannyosu]

I can confirm this is still an issue. Whatever the latest build is (beta or full), it's always tagged latest.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[benliles]

Only the latest tag is being applied. RC and other tags are missing.

[csana]

I can confirm this issue too.
The latest tag is beeing applied to the most recent build, isntead of the most recent release, it's fustrating.

[ZetaPhoenix]

In addition to homeassistant/raspberrypi3-homeassistant I see homeassistant/odroid-c2-homeassistant also has the same issue.

[GuitarSkater]

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

[benliles]

???

This has nothing to do with code changes to Home Assistant itself but the raspberry pi deployment. It's still completely broken.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[benliles]

Still a problem

On Sun, Jul 7, 2019, 5:25 AM stale[bot] [e-mail] wrote:

There hasn't been any activity on this issue recently. Due to the high
number of incoming GitHub notifications, we have to clean some of the old
issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check
if that solves the issue. Let us know if that works for you by adding a
comment 👍
This issue now has been marked as stale and will be closed if no further
activity occurs. Thank you for your contributions.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13543?email_source=notifications&email_token=AAAPWZYIZJ64Q26D44VBUGDP6HODTA5CNFSM4EYF5VB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLKQMY#issuecomment-508995635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPWZ6WVVZFEPYRUXGIZL3P6HODTANCNFSM4EYF5VBQ
.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[benliles]

This does appear to have been fixed finally.

[frenck]

yep! We have now 1 single meta image 🎉