-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora 29 (beta): issue with additional packages #56
Comments
I am happy that you like this role and I am sincerely grateful for that you report this even if now Fedora 29 is in beta. It can be that this exists in other distributions also or other version of Fedora which I have not yet automated tests for. The distributions I currently have automated tests on are the following:
The feature in this role you experience problems with is something I recently added and have not got the time to test it out in too much detail. But I would like to know a bit more of your setup so I can see if there is a good way to avoid this problem in the future or not. Below are some questions:
Cheers! |
quick first feedback:
this was run right after running/applying your role and getting this:
I am still unsure about this conflict.
|
OK, one more: I rm-ed my symbolic links to venv-binaries and started a new shell to make sure I use fedora's ansible(-playbook). And I tried to reapply the role to my localhost. This gives me:
docker-envs exists ... I decided to rm it (it was fom august), rerun still fails. |
maybe I "solved" it for now, cleaned up a mixed setup: had older version of your role installed as root etc / stay tuned ;-) ah, not yet:
|
interesting, this works fine:
enough for now, bye |
Thanks @stefangweichinger for all the information you have given, much appreciated! I was a bit afraid when I added Reproducing this in some easy way using some Vagrant boxes on VirtualBox would help me to fix this issue. Hope I will get time to do it because right now I trying to add the Fedora distribution into the automated tests and are close to fix that. Cheers! |
So where is the vagrant file? ;-) |
note: as F29 will be released tomorrow there seem to be some things going on. The docker-ce-repo at docker.com does not yet provide a docker-ce-package for F29, this leads to failing installation here etc Additionally I see mismatches between systemd-service files from fedora and docker-ce.repo (path to docker-binary "docker" vs. "dockerd" etc). tldr: we might have to wait a few days for things to calm down? |
@stefangweichinger many thanks for the update! As you suggest we can wait and I will make some updates in the tests to prepare for F29. Will let you know I have done that. Cheers! |
see https://download.docker.com/linux/fedora/29/x86_64/ (nothing stable yet) |
Just an update from my side. Fedora has release a Vagrant box for 29 so I added that but Docker does not install yet because of missing The tests I am executing etc you can find here: https://github.com/haxorof/ansible-role-docker-ce/tree/master/tests. Read the README.md for prerequisites. If you for example would like to try it out yourself. It should now be possible for you to go into the tests directory and from there write the following to just execute all tests on F29: ./test.sh t_ fedora/29 The ./test.sh t_no_config fedora/29 |
@haxorof : great news, thanks for the update etc / will look into that in the next days, tmrw holiday here, so I will spend some time offline ;-) |
@haxorof : did a short test ... unfortunately running the test script for fedora/29 sends my machine into high load and swapping :-( Multiple ruby-mri processes, I don't know. My box has a core i7-6700 and 16 gigs of RAM, I don't know what you try to run in your tests but normally the machine should be enough ;-) (?) |
@stefangweichinger: that was interesting. I actually run with a machine that have lower specs than you. Tests just installs Docker with my role in different ways to verify config etc. When you run any Vagrantfile does it behave in the same way? |
@haxorof I removed and reinstalled vagrant completely, I still get dozens of these processes:
So it seems related to this plugin install failing. ps: If I execute that on the shell:
|
Thanks @stefangweichinger! I will check if that plugin is unnecessary because now it is specified in a file which is executed when vagrant command is used in the tests directory. you could try to rename that file and just make sure the plugin Cheers! |
@haxorof commenting the line "vagrant-share" out of that file helps to bring up the machine, it is downloading now. I hope the boxes are kept/cached on my machine after the initial download? |
@haxorof this leads to numerous other issues, I don't know. Your test script also fails in the end because the setup of the box wants to use the sharing-features somehow, at least it throws an error. I removed and reinstalled vagrant, and it gives me various errors around its plugins. Maybe related to F29, maybe not, I don't know yet |
Hi @stefangweichinger! Sorry for now answering you earlier but has been a bit busy. Thank you for trying running the tests but I think I need to go back and review what requirements there are to run the tests. Also today I noticed other issues similar to the pip related stuff you saw in F29 so I think I will have some time on Sunday to check all this. In the meantime I think you can wait for me to look into the things written above. Cheers! |
@haxorof ok, I see. No problem, so far I can use docker for my purposes. All the vagrant part is not necessary for me (although I would like to be able to use it, sure ... and learn from it). Looking forward to the next steps, Stefan |
After some changes I now have a test suite that passes for Fedora version 25, 26, 27 and 28. For Fedora 29 I cannot see it is possible to install Docker yet from the nightly build because of missing dependencies. Will wait a bit until Docker have some working nightly build. |
Just would like to inform you that it is now possible to successfully install Docker on Fedora 29 from the nightly Docker channel. Example that works on Fedora 29 cloud image:
Cheers! |
I have run through the following test on Fedora 29 cloud image and it work. ---
- name: Test using PiP to install SDK, compose and stack
hosts: test-host
vars:
docker_channel: nightly
docker_sdk: true
docker_compose: true
docker_stack: true
roles:
- haxorof.docker-ce
post_tasks:
- name: Test hello container
become: yes
docker_container:
name: hello
image: hello-world
- name: Test hello service
become: yes
docker_service:
project_name: hello
definition:
version: '3'
services:
hello:
image: "hello-world"
- name: Test install of Docker compose not using PiP
hosts: test-host
vars:
docker_channel: nightly
docker_compose: true
docker_compose_no_pip: true
roles:
- haxorof.docker-ce @stefangweichinger Shall I close this issue? |
ok with me, as you like. Thanks for your tests, etc Sidenote: pls note the test-dir, it's new ;-) -> https://download.docker.com/linux/fedora/29/x86_64/test/Packages/ So they seem to prepare something. |
Thanks for the helpful role!
I understand that I use it on a beta (until next week or so?) of Fedora 29, but maybe the issue hits other installations as well:
when I apply the role I get:
(full paste to include all info ...)
I am using ansible provided by Fedora repo:
The text was updated successfully, but these errors were encountered: