-
Notifications
You must be signed in to change notification settings - Fork 392
Build successful but no effect inside containers #924
Comments
I've created a small example to provide some more information: Includes:
After checkout you can run What I am doing wrong? 😢 |
I have tried your example , at least command Related issue: |
Hey Voronenko, thank you very much for your time and feedback. ...and yes, the example is really working! Im kind of doomed because it seems like my issue is somewhere else between WSL (Windows-Subsystem for Linux), docker and ansible-container - I have no clue atm. At least I know now that I really have an issue and its not about me^^ I'll try to investigate this further and will give feedback. I've tested for your mentioned issue #937 but I am not effected by that. Thanks again :) |
Offtopic, I am also using docker on windows with 64G ram to offload builds from my linux notebook, but I just turned on setting for windows docker daemon to listen on tcp port 2375. For WSL - just works w/o additional tools; |
@Nexlo Can you update on your progress? If it is still issue - we need to transform it into reproducible scenario. |
Hey Voronenko, I've tested ansible-container & docker without the docker-relay to my windows.
during execution of a simple With the relay active and using my docker on my windows machine everything is working fine - beside the fact, that no roles are applied during execution of Still after further research and investigation I have no clue what this is exactly about. @Voronenko which informations are missing for reproduction? Thanks for any help! :) Further system information:SumUp:
Output: docker version
Output: docker info
|
Well, issue might relay mostly to your system. From the WSL (based on ubuntu:xenial) I am able to successfully compile, for example this demo with ansible-container. Python 2.7.12 so I would say root cause is somewhere near setup you have mostly docker relay (npiperelay tool) ? Can you try to simplify your windows setup ? |
Hey Voronenko, I was able to exclude "npiperelay tool" by simply setting my environment var 'DOCKER_HOST'. Sadly now I run into (#602 ). In Windows we dont have file sockets, right? see. Also mentioned in docker docs, see here. So, ya... I'd say I am running circles^^ Let me mention again, actually with npipetool enabled the execution is running without any errors.
I only have this (for me) solid reproduceable fail, that nothing really happens to the containers... :/ (2x in Ubuntu 16.04 & 1x in Debian 9 stretch)
Sorry, what do you mean exactly? My windows has a lot of stuff installed - but involved into this topic should be only the WSL and "Docker for Windows"? Other than that, I've researched for a PowerShell script to kickstart WSL:
I appreciate every further help or hints :) Thanks! |
ISSUE TYPE
container.yml
OS / ENVIRONMENT
OS / ENVIRONMENT (additional)
I am running Windows Subsystem for Linux on Windows 10 with connected docker client from my linux to my windows host (docker-for-windows). Works fine so far. I dont think/hope its related to this here.
SUMMARY
I am new with ansible-container ;) ..have a little doubt that I use something wrong. Thats why I've opend a documentation.
After successful
ansible-container build
I expect the tasks defined in my role which is assigned to the container have been executed inside the container.Executing
ansible-container --debug build
says:Applied role to service
Committed new layer as image
andAll images successfully built
I've initialized the role via
ansible-galaxy init apache2-server
and added afterwards inroles/apache2-server/tasks/main.yml
a task to install vim.EXPECTED RESULTS
The packages are installed inside the container.
ACTUAL RESULTS
Packages are not installed inside the container.
OUTPUT build (end partial)
QUESTIONS
Do I have to select/use this new create image manually?
Are my tasks really executed? (see output)
Thanks in advance for any help! :)
The text was updated successfully, but these errors were encountered: