Why do we have to push an image to a registry?
-
I moved the sysbox talk to the other topic, please keep the thread to a single topic. Otherwise, it's very hard to track discussions.
-
wrote on Oct 23, 2020, 10:34 PM last edited by Lonkle Oct 23, 2020, 10:34 PM
--no-pushstopped working for me (it still builds, but doesn't skip the push). I checked theboxpatch and it's there. I checked the CLI tool and it still has the option. The Build Service Bot got more updates, was there an issue with the Bot. Can you reproduce this @girish with the latest Cloudron Build Service app? -
wrote on Oct 23, 2020, 10:40 PM last edited by
I just checked and this is literally the only commit you made after
v1.2.1that could have broken this, it could be related if you can reproduce this at least. I'll try to roll back my Build Service Version in the meantime.Oh, the commit that could have caused this: https://git.cloudron.io/cloudron/cloudron-build-service/-/commit/5012542ecd7d538a37fe8f84cfab096c588f0ac2
-
wrote on Oct 26, 2020, 10:42 PM last edited by Lonkle Oct 26, 2020, 10:44 PM
@girish I swear this
--no-pushfeature worked perfectly for me until the Build Service got updated. Does it still work on your install (since we're both running onmasterrn - maybe it still works on stable, with the small patch, and it's a separatemasterissue - jus' wanna check)? -
wrote on Oct 26, 2020, 11:00 PM last edited by
The irony that that commit was called "Fix typoe"
-
wrote on Oct 27, 2020, 6:31 PM last edited by
Just tested and it's fixed. You can mark this as solved. Thank you!
️ -
wrote on Nov 7, 2020, 11:49 PM last edited by yusf Nov 7, 2020, 11:49 PM
Does this mean that we can also host the Cloudron build service on production machines, or am I mistaken?
-
Does this mean that we can also host the Cloudron build service on production machines, or am I mistaken?
wrote on Nov 8, 2020, 12:57 AM last edited by@yusf no, that would be this scenario
https://forum.cloudron.io/post/16249 -
Does this mean that we can also host the Cloudron build service on production machines, or am I mistaken?
wrote on Nov 8, 2020, 3:04 PM last edited by@yusf said in Why do we have to push an image to a registry?:
Does this mean that we can also host the Cloudron build service on production machines, or am I mistaken?
Well, I run it only on a dev machine since I only use Cloudron to dev. But tbh, after 100s of builds. All of the other apps are still running smoothly so it's not recommended because it's the only app with the
dockeradd-on and thus could technically mess with other apps. It has never done so, I just think they'd rather not have the responsibility of calling it "production-ready" even though in my dev environment, it gives me no issues. I would feel comfortable running this in production tbh. The worry is if it ever bugged. But I can actually work around that by accounting for it using a Cloudron add-on I'm building (Dot the Repair Bot) so even though it's never happened, if I account for the Build Service being able to destroy containers / data outside it's sandbox (what the devs mean when they say it's not for production), I can have them auto-restored by Dot.But if Dot got destroyed by the Build Service I'd be screwed.