https://www.spryker.com logo
Join Slack
Powered by
Hello engineers, I am happy to share news about K...
# docker
p
Hello engineers, I am happy to share news about Kibana 6 support, docker-sync improvements and that painful bug with docker containers which could not be stopped (we know, it was painful. Sorry for taking it so long).  1.9.3 - 1.8.1 Improvements • Kibana v6 is supported Bug fixes • Fixed the behaviour when docker container(s) cannot be stopped on Unix-like operating systems. • Fixed static MySQL port binding. • Fixed generation of 
.ssh/known_hosts
into containers. • [sync] Allow using a custom image for docker-sync. • [sync] Mount mode for sync volume changed to 
nocopy
• [sync] Unison’s strategy changed from 
prefer
to 
force
. • Permission for binaries is now set before installation script. • The direct mount for the composer cache has been removed. More details:  • Releases: https://github.com/spryker/docker-sdk/releases • Docker SDK: https://documentation.spryker.com/installation/spryker_in_docker/docker_sdk/docker-sdk.htm Please, try it, use it, and send us your feedback! Dmytro
👍 1
s
[sync] Unison’s strategy changed from prefer to force.
This makes me feel physically ill. Which direction is enforced?
(too many bad experiences with forced syncs, nothing to do with Spryker especially) Thank you for the new version, all fixes are very welcome 🙏
p
Thomas, it is 2-way: the file with the latest change time always wins.
s
Hmmmm so that means I can possibly "oversync" code in my CWD due to a sync error?
h
prefer
option just makes copies of conflicting files. Is that better to have hundreds of conflicts to resolved that way? Also I do not see problems with force sync in development case, as the only source of file changes in containers are console commands or caching mechanisms. And your code would always be guarded by git on host machine.
I would recommend to have PHP with all extensions on host machine and run composer and build commands at the host.
m
since the last changes of unison sync I have a lot of sync problems... aboveall when i run composer update or install... it seems that the file are not properly synced... @high-pencil-62400 it is not possible to have on host machine alls php extension compiled and running... How can we change back the strategy?
h
What kind of problems?
Actually to run build commands and composer you would need standard PHP without extensions. But each composer install command would need --ignore-platform-reqs.
m
No. It is not correct. U can have problems with php version etc....
Mike Kalinin  [17:06 Uhr] What kind of problems? It happened that the sync is very very very slow.... (app_sync -> host) and that inconsistent files are present after composer update or install.... not sure what is right.. on unison or local... and also after i.e. deployment script (just run a lot of build commands). Before I didnt have such problems.. I think that is related to the force strategy...
and i am always disappointed with run composer or build command local... otherwise there is no reason to use docker or vagrant or some other virtualization...
h
What kind of problems do you have with 
force
option?
m
just what i wrote in my last 2 comments... slow sync and inconsistent sync.. with previuos version i didn't faced any problem about sync
h
I got your point. We are investigating the topic.
Open in Slack
PreviousNext
Powered by