# Upgrade succeeded on Pi-Hole in a Container Station image on QNAP NAS

**URL:** <https://discourse.pi-hole.net/t/upgrade-succeeded-on-pi-hole-in-a-container-station-image-on-qnap-nas/27195>\
**Category:** Beta 5.0\
**Created:** [January 20, 2020, 10:39pm UTC](https://discourse.pi-hole.net/t/upgrade-succeeded-on-pi-hole-in-a-container-station-image-on-qnap-nas/27195 "2020-01-20T22:39:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cecoates](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/cecoates/32/11845_2.png) [@cecoates](https://discourse.pi-hole.net/u/cecoates)\
**Post date:** [January 20, 2020, 10:39pm UTC](https://discourse.pi-hole.net/t/upgrade-succeeded-on-pi-hole-in-a-container-station-image-on-qnap-nas/27195/1 "2020-01-20T22:39:09Z")

</div>

I've been running Pi-hole in a ubuntu-xenial:latest LXC container on my QNAP following these steps:

[https://forum.qnap.com/viewtopic.php?t=147501#p709656](https://forum.qnap.com/viewtopic.php?t=147501#p709656)

I was able to upgrade to Pi-hole 5 without any complications by opening up a command prompt to the container and running the commands here:

[https://pi-hole.net/2020/01/19/announcing-a-beta-test-of-pi-hole-5-0/](https://pi-hole.net/2020/01/19/announcing-a-beta-test-of-pi-hole-5-0/)

The only oddity to running Pi-hole in a container is that there doesn't seem to be any way to get Pi-hole to identify/list individual clients. Only the NAS itself is listed as a client for all queries.

But that may just be a quirk of using a container on a NAS, however (since the NAS handles assigning containers IPs via "Virtual Switch").

[https://www.qnap.com/en/how-to/tutorial/article/how-to-use-and-set-up-your-network-virtual-switch/](https://www.qnap.com/en/how-to/tutorial/article/how-to-use-and-set-up-your-network-virtual-switch/)

Following any of these guides doesn't solve it:

> [@How do I configure my devices to use Pi-hole as their DNS server?](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245):
>
> Three methods Generally, there are three different methods that will enable devices on your network to be protected by Pi-hole. 1. Define Pi-hole's IP address as the only DNS entry in the router Rationale Only is italicized here for a reason: Pi-hole needs to be the only DNS server because it intercepts queries and decides whether or not they should be blocked. If you have other DNS servers configured, you may be sent to the correct domain, bypassing Pi-hole completely. Because of this, we re…

> [@How do I use Pi-hole's built in DHCP server (and why would I want to)?](https://discourse.pi-hole.net/t/how-do-i-use-pi-holes-built-in-dhcp-server-and-why-would-i-want-to/3026):
>
> Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often [set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245), which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. W…

> [@How do I show hostnames instead of IP addresses in the dashboard?](https://discourse.pi-hole.net/t/how-do-i-show-hostnames-instead-of-ip-addresses-in-the-dashboard/3530):
>
> There are two ways to accomplish this: use Pi-hole's built in DHCP server use your router's DHCP server and modify /etc/hosts on your Pi-hole machine Use Pi-hole's DHCP server When you enable Pi-hole's DHCP server, you have the option to assign DHCP reservations and pair them with a hostname. Just make a reservation for every device on your network. Edit /etc/hosts on your Pi-hole The other option is useful if you want to keep your existing DHCP server (usually your router) and ju…

[https://discourse.pi-hole.net/t/why-should-pi-hole-be-my-only-dns-server/3376](https://discourse.pi-hole.net/t/why-should-pi-hole-be-my-only-dns-server/3376)

Otherwise works great, just providing those details as background to clarify it isn't an issue specific to Pi-hole 5.

Question: does the "already up-to-date" message mean the "pihole checkout web release/v5.0" command wasn't necessary? Or just that one specific step of the command is already-up-to-date?

Out of curiosity what would happen if someone didn't run it?

```auto
ubuntu@pihole-qnap:~$ pihole checkout web release/v5.0                                                                                                                                                                                                                                                                             
  Please note that changing branches severely alters your Pi-hole subsystems                                                                                                                                                                                                                                                       
  Features that work on the master branch, may not on a development branch                                                                                                                                                                                                                                                         
  This feature is NOT supported unless a Pi-hole developer explicitly asks!                                                                                                                                                                                                                                                        
  Have you read and understood this? [y/N] y                                                                                                                                                                                                                                                                                       
                                                                                                                                                                                                                                                                                                                                   
  [✓] Fetching branches from https://github.com/pi-hole/AdminLTE.git                                                                                                                                                                                                                                                               
  [i] 19 branches available for Web Admin                                                                                                                                                                                                                                                                                          
                                                                                                                                                                                                                                                                                                                                   
  [✓] Switching to branch: 'release/v5.0' from 'refs/heads/master'                                                                                                                                                                                                                                                                 
  [i] Already up-to-date.                                                                                                                                                                                                                                                                                                          
ubuntu@pihole-qnap:~$       

```

---

<div class="post-metadata">

**Author:** ![cecoates](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/cecoates/32/11845_2.png) [@cecoates](https://discourse.pi-hole.net/u/cecoates)\
**Post date:** [January 20, 2020, 10:42pm UTC](https://discourse.pi-hole.net/t/upgrade-succeeded-on-pi-hole-in-a-container-station-image-on-qnap-nas/27195/2 "2020-01-20T22:42:32Z")

</div>

The web interface seems a lot "zippier". I can't tell if I'm just imagining it, but I'd swear there's less lag/shorter load times when clicking around.