cloudron install w/o registry

[timconsidine]

Generally the recommended way from docs is

• docker build etc
• docker push etc
• cloudron install etc

Of course I try to be a good boy and follow this.
But to save a step and lots of time during dev, is it possible to do something like cloudron install --image ./reponame:tag ?
So it installs from built image on local device ?

[atridad]

this is a lot more complicated to implement well since backups and restores rely on access to the container from a repo to run. Doing this would mean the backup/restore process would need to be disabled or the source would need to be editable.

[timconsidine]

@atridad thanks for the explanation - I will stick to the normal process !

[girish]

@timconsidine said in cloudron install w/o registry:

So it installs from built image on local device ?

I was going to reply saying this was 'impossible' but I have since learnt this might actually be a good idea.

Apparently, there are 2 new commands docker docker save and docker load that can pipe images - https://dockerlabs.collabnix.com/beginners/saving-images-as-tar/ . This does break cloudron backup/restore since images are not part of a backup but in development mode, I can see this being considerably faster than having to push and download from a hub/registry each time.

Something to consider for a future release.

[timconsidine]

@girish thanks
yes, during development process was my 'use case'
just saving time
no big problem to continue as is for now
maybe interesting benefit in future

[atridad]

@girish perhaps it can allow restores but only via the cli? And then you can pass on your local backup or another image somewhere else. Being able to customize the image used for backups would be helpful. I ran into an issue with this earlier for someone else’s cloudron

[girish]

@atridad right. I guess we need some sort of 'development mode' flag for such apps which will ask the user to provide an image name optionally during restore.