Skip to content
This repository has been archived by the owner on Dec 8, 2019. It is now read-only.

/unison initial state #10

Open
alexgorbatchev opened this issue Feb 23, 2016 · 2 comments
Open

/unison initial state #10

alexgorbatchev opened this issue Feb 23, 2016 · 2 comments

Comments

@alexgorbatchev
Copy link

I don't completely understand how to get unison to work at boot time. I'm trying to keep my source folder syncing from local to container. When container starts, it expects the source to be there already. README suggests and my quick test confirms, that upon boot of the container, /unison is empty and needs to be synced to.

What is the suggested to way to work in this scenario? I feel this is a pretty standard setup.

@onnimonni
Copy link

I'll just startup the data container first, sync, and then start all of the other containers.

@leighmcculloch
Copy link
Owner

@alexgorbatchev What would we need to change about the initial state of the docker image to fix this? I'm happy to look into making this initial state easier.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants