by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
bcurran3
@bcurran3
I'm also assuming you have not messed with the mount point - "{{ heimdall_data_directory }}:/config:rw"
kiwilad-nz
@kiwilad-nz
'/path/to/appdata/config' - Change that to a valid path.
Btw, what I did with my config was copy everything into "/inventories/sample/group_vars/nas.yml" from "/group_vars/all.yml" - and hash out the lines that weren't changed.

for the changed lines, leave them unhashed. Effectively ansible does a comparison between the files to notice any changes made.

So if you are using must services, you will need to set them to servicename="true" for starters.

Then further down for that service, look for the associated config and make sure it is correct such as directory paths etc.

Wessel van Norel
@delgurth_gitlab
Hi,
First of all, thanks for creating this project. So far it's a nice experience. I've a few questions. It seems the requirements are out of date. I ran into an issue with Samba and macOS and the icon it shows on macOS. In the end it was the result of using bertvv.samba 2.7.0 and not 2.7.1 (the specific issue: bertvv/ansible-role-samba#39). Should I create a pull request for this?
The gitlab stuff didn't work out of the box. The minimum memory requirements for gitlab are 8GB. Guess because of my system not having swap, it failed to run properly with the 4GB limit set in the docker configuration.
Also the gitlab gid and uid resulted in conflicts for me. Do we really want to set those values or can't we let the system pick them so you won't get into a conflict?
Wessel van Norel
@delgurth_gitlab
With glances I got a lot of apparmor warnings, which I "fixed" by setting "security_opts: apparmor=unconfined"
Wessel van Norel
@delgurth_gitlab
I also ran into davestephens/ansible-nas#241, guess this should be something you can configure. Direct doesn't work for me. It seems that the influxdb port is also not configured correctly in the template. Should I do both things in the same pull request or do I need to make 2 pull requests out of that?
bcurran3
@bcurran3
@delgurth_gitlab - You might want to update, the ansible-role-samba was updated to 2.7.1 back on April 24th. :) I don't know about the other stuff...
jestrada2999
@jestrada2999
About to dive in, wish me luck guys!
kiwilad-nz
@kiwilad-nz
GL dude
kiwilad-nz
@kiwilad-nz
quick question - So if it was Ansible that wasn't working currently for 20, can I do an upgrade after it's all set up? Obviously if I ever need to run ansible again, I would need to wait
@bcurran3 - that would be correct in my thinking yea?
bcurran3
@bcurran3
Yes. Google it, but it's basically as easy as "do-release-upgrade -d"
kiwilad-nz
@kiwilad-nz
Yea, but does it break anything?
other than running ansible
kiwilad-nz
@kiwilad-nz
image.png
Added the logo and it looks beautiful along with webmin
bcurran3
@bcurran3
Not sure if it will break right now. It's not really about Ansible or Ansible-NAS but a module that AN uses. You can upgrade and let us know if it breaks or not. :) I might try it later this week in a VM when I have time and can report back.
mikey9060
@mikey9060
Hi there , i need some advice to set up ufw for ansible nas . Do i simply allow the application ports i use or are there other steps to cover ? Thanks in advance.
Koen Vervloesem
@koenvervloesem
Docker and ufw have quite a complex interaction. By default it does very unexpected things, see here: https://github.com/chaifeng/ufw-docker
xeijin
@xeijin

Hello, does anyone know how I would pass the ansible ZFS module a passphrase?

the following just hangs for me

    - name: create zfs dataset - barbican/home
      zfs:
        name: "{{ zfs_pool_name }}/home"
        state: present
        extra_zfs_properties:
          encryption: aes-256-gcm
          keyformat: passphrase
          mountpoint: legacy
mikey9060
@mikey9060
Thanks Koen for the info. Recently read your dutch guide on ansible. Top !
Julian Wachholz
@julianwachholz
Are there any example grafana templates one could use as starting points?
nevermind I found it
Julian Wachholz
@julianwachholz
really struggling to find a good way to add network traffic statistics to the dashboard though :(
PurpleNinja225
@PurpleNinja225
recently built on ubtu18.04.4 everything was running smooth until the playbook tries to restart docker, journalctl -xe shows that it "failed to start daemon: error initializing graphdriver: driver not supported" I'm using ZFS and have changed "docker_storage_driver" in the nas.yml to reflect such. I feel like im messing something up soemwhere
Patrick Saindon
@PatSaindon_twitter
docker_storage_driver is not for your media storage file system, but for the image registry. Don't change it unless you know what your are doing.
PurpleNinja225
@PurpleNinja225
thanks for the tip! I went over to the geerlingguy docker github and was able to figure it out, changing the storage driver back to default in etc/docker/daemon.json
Julian Wachholz
@julianwachholz
@PurpleNinja225 I set up Docker to use my ZFS tank as well, a requirement mentioned in the docs is that /var/lib/docker must be mounted on a ZFS as well, they have an easy to follow guide to do so: https://docs.docker.com/storage/storagedriver/zfs-driver/#configure-docker-with-the-zfs-storage-driver
and instead of creating an entirely different pool I just created a separate dataset in my existing pool and set the mountpoint for that to /var/lib/docker
hunnid100
@hunnid100
Hi! I am new to this and I really appreciate the ansible-nas project. I was able to get it to work for a while but then I was trying to upgrade my nextcloud server and I broke something. So I tried to start over. I used Portainer to removing all my images and containers and then removed the docker folder recursively in the terminal. Now when I try to rerun the ansible playbook I get the following error: "fatal: [ansible-nas]: FAILED! => {"changed": false, "msg": "Error pulling portainer/portainer - code: None message: open /mnt/storage/docker/data/tmp/GetImageBlob930152423: no such file or directory"}" Do you have any ideas on what I can do?
Jesse Goerz
@jgoerz
Upgrading broke my setup as well. I can't even get into Portainer. In fact, none of the containers are running. It appears that the new "create your own inventory and nas.yml files" is not working for me either.
Jesse Goerz
@jgoerz
Looks like the upgrade ignored my docker_home and docker_storage_driver overrides. :scream: dang. Might have to start over from scratch.
TASK [geerlingguy.docker : Ensure Docker is started and enabled at boot.] ****************************************************************** fatal: [192.168.x.x]: FAILED! => {"changed": false, "msg": "Unable to start service docker: Job for docker.service failed because the control process exited with error code.\nSee \"systemctl status docker.service\" and \"journalctl -xe\" for details.\n"}
For some reason, can't get systemd to play nice.
Jesse Goerz
@jgoerz
ok, so got it back. Here's how I fixed it. It appears docker_home and docker_storage_driver overrides in the nas.yml do not work. So override both of those in the group_vars/all.yml file if you're not using the defaults. I had to ssh into the machine and modify /etc/docker/daemon.json and set the storage driver to zfs, otherwise it just kept bombing. Once it completed the playbook once, it was fine again.
PurpleNinja225
@PurpleNinja225
@julianwachholz Thanks! That docker article was immensely helpful!
Tomas Strand
@straend
Tips on how to generate Lets Encrypt certificates for Traefik? tried stopping traefik container, removing it from docker, no success. And no success with changing ansible_nas_domain in my yaml either.
I just keep getting traefiks default cert
Julian Wachholz
@julianwachholz
@straend your hostname and port forwards are all setup correctly? i once had the same issue I removed the traefik container entirely and let ansible rebuild it
I have added a samba_user but didn't change the default shares but now new files are owned by root:root :|
Tomas Strand
@straend
@julianwachholz yes, from what I can see I have the correct A and CNAME (for *.mynas.something) and 80+443 forwarded
Tomas Strand
@straend
echo | openssl s_client -showcerts -servername wallabag.mynas.something -connect wallabag.mynas.something:443 2>/dev/null | openssl x509 -inform pem -noout -text gives me Issuer: CN = TRAEFIK DEFAULT CERT from a vps
and I can load the wallabag install fine on my phone over 4G (with the default traefik cert) tried removing the container with -v to get rid of volumes but no luck, docker system prune after traefik was stopped and removed didn't do any better either
Tomas Strand
@straend
Well, solved it by changing to use dns-challenge and using a wildcard cert main = "*.{{ ansible_nas_domain }}"
mattaze
@mattaze
likely a simple question - only need one plex directory, how can the other directories be disabled from being created? such as plex_podcasts_directory, would plex_podcasts_directory: none be enough?
kiwilad-nz
@kiwilad-nz
@mattaze edit the ansible-nas/tasks/plex.yml file and remove the directories or # them out
you can always just edit the docker container after as well.