F5F Stay Refreshed Hardware Desktop The cache loading process fails.

The cache loading process fails.

The cache loading process fails.

_
75
08-02-2016, 02:04 AM
#1
You're encountering a Docker error related to data types. The messages indicate that certain containers expect bytes-like objects but you're passing strings instead. Make sure all inputs match the expected format—convert strings to bytes or adjust your configuration accordingly.
_
_victorplayer_
08-02-2016, 02:04 AM #1

You're encountering a Docker error related to data types. The messages indicate that certain containers expect bytes-like objects but you're passing strings instead. Make sure all inputs match the expected format—convert strings to bytes or adjust your configuration accordingly.

D
Dridri2002
Junior Member
47
08-02-2016, 03:12 PM
#2
Here’s a revised version of your content:

Just to clarify, this is my .env file for Lancache Spoiler GNU nano 5.2. Modified ## Refer to the "Settings" section in README.md for further information ## Ensure this is enabled when using a load balancer, or disable it if you have separate IPs for each service. ## If you're working with a monolithic setup (the default), keep this set to true USE_GENERIC_CACHE=true ## List the IP addresses your Lancache monolithic instance can reach on ## Provide one or more IPs separated by spaces—these will be used when resolving hostnames via LancacheNet. Having multiple IPs can boost cache loading speed for certain services (e.g., Steam) ## Reminder: This adjustment only impacts DNS; monolithic and sniproxy will still connect to all IPs by default LANCACHE_IP=192.168.1.20 ## The IP assigned to the host that the DNS server should target DNS_BIND_IP=192.168.1.20 ## DNS resolution for forwarded lookups uses UPSTREAM_DNS=8.8.8.8 ## Directory where cached data is stored ## By default, this points to a folder relative to the docker-compose.yml file CACHE_ROOT=./lancache ## Modify this to adjust the cache size (default 1,000,000 bytes) ## If you have extra storage, increase it accordingly ## The cache server will remove outdated content based on usage if it nears this threshold. ## Set this below your actual available space CACHE_DISK_SIZE=100,000 bytes ## Change this to tailor the size of the Nginx cache manager (default 500KB) ## Avoid making major changes. The defaults are sufficient for handling up to 8TB of cache. Raising it will likely lead to performance issues and possible cache failure. CACHE_INDEX_SIZE=500 bytes ## Adjust this to control how long cached items stay (default: 3,650 days) ## Set the timezone for your Docker containers, important for accurate log timestamps (default: Europe/London)
D
Dridri2002
08-02-2016, 03:12 PM #2

Here’s a revised version of your content:

Just to clarify, this is my .env file for Lancache Spoiler GNU nano 5.2. Modified ## Refer to the "Settings" section in README.md for further information ## Ensure this is enabled when using a load balancer, or disable it if you have separate IPs for each service. ## If you're working with a monolithic setup (the default), keep this set to true USE_GENERIC_CACHE=true ## List the IP addresses your Lancache monolithic instance can reach on ## Provide one or more IPs separated by spaces—these will be used when resolving hostnames via LancacheNet. Having multiple IPs can boost cache loading speed for certain services (e.g., Steam) ## Reminder: This adjustment only impacts DNS; monolithic and sniproxy will still connect to all IPs by default LANCACHE_IP=192.168.1.20 ## The IP assigned to the host that the DNS server should target DNS_BIND_IP=192.168.1.20 ## DNS resolution for forwarded lookups uses UPSTREAM_DNS=8.8.8.8 ## Directory where cached data is stored ## By default, this points to a folder relative to the docker-compose.yml file CACHE_ROOT=./lancache ## Modify this to adjust the cache size (default 1,000,000 bytes) ## If you have extra storage, increase it accordingly ## The cache server will remove outdated content based on usage if it nears this threshold. ## Set this below your actual available space CACHE_DISK_SIZE=100,000 bytes ## Change this to tailor the size of the Nginx cache manager (default 500KB) ## Avoid making major changes. The defaults are sufficient for handling up to 8TB of cache. Raising it will likely lead to performance issues and possible cache failure. CACHE_INDEX_SIZE=500 bytes ## Adjust this to control how long cached items stay (default: 3,650 days) ## Set the timezone for your Docker containers, important for accurate log timestamps (default: Europe/London)

R
ReeceTheRebel
Junior Member
39
08-02-2016, 04:00 PM
#3
I encountered a similar issue. I found a fix for it. Starting the process... Removing lancache_monolithic_1 Rebuilding lancache_dns_1 ... Rebuilding 724ebceea3ad_lancache_monolithic_1 ... Rebuilding lancache_dns_1 ... Error: for 724ebceea3ad_lancache_monolithic_1 a bytes-like object is needed, not 'str' Error: for lancache_dns_1 b'cannot stop container: 7e3206bba4ef9c80c5bc6cb00685dc6e11bf1b0875d56628dc36a34d7d05595b: permission denied' Error: for monolithic a bytes-like object is required, not 'str' Error: for dns b'cannot stop container: 7e3206bba4ef9c80c5bc6cb00685dc6e11bf1b0875d56628dc36a34d7d05595b: permission denied" Traceback (most recent call last): File "/usr/lib/python3/dist-packages/docker/api/client.py", line 261, in _raise_for_status response.raise_for_status() File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.22/containers/9a71099a94f4e11100adab2e0ab4e3f6d291652635a22338ceae1d3fb85611a4/start During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/compose/service.py", line 625, in start_container container.start() File "/usr/lib/python3/dist-packages/compose/container.py", line 241, in start return self.client.start(self.id, **options) File "/usr/lib/python3/dist-packages/docker/utils/decorators.py", line 19, in start_container if "driver failed programming external connectivity" ...
R
ReeceTheRebel
08-02-2016, 04:00 PM #3

I encountered a similar issue. I found a fix for it. Starting the process... Removing lancache_monolithic_1 Rebuilding lancache_dns_1 ... Rebuilding 724ebceea3ad_lancache_monolithic_1 ... Rebuilding lancache_dns_1 ... Error: for 724ebceea3ad_lancache_monolithic_1 a bytes-like object is needed, not 'str' Error: for lancache_dns_1 b'cannot stop container: 7e3206bba4ef9c80c5bc6cb00685dc6e11bf1b0875d56628dc36a34d7d05595b: permission denied' Error: for monolithic a bytes-like object is required, not 'str' Error: for dns b'cannot stop container: 7e3206bba4ef9c80c5bc6cb00685dc6e11bf1b0875d56628dc36a34d7d05595b: permission denied" Traceback (most recent call last): File "/usr/lib/python3/dist-packages/docker/api/client.py", line 261, in _raise_for_status response.raise_for_status() File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.22/containers/9a71099a94f4e11100adab2e0ab4e3f6d291652635a22338ceae1d3fb85611a4/start During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/compose/service.py", line 625, in start_container container.start() File "/usr/lib/python3/dist-packages/compose/container.py", line 241, in start return self.client.start(self.id, **options) File "/usr/lib/python3/dist-packages/docker/utils/decorators.py", line 19, in start_container if "driver failed programming external connectivity" ...

S
SkyQUEEN4756
Member
50
08-02-2016, 10:46 PM
#4
Yes, someone found a way to solve it.
S
SkyQUEEN4756
08-02-2016, 10:46 PM #4

Yes, someone found a way to solve it.

C
chayden2k6
Member
119
08-04-2016, 05:12 AM
#5
I resolved it by running it in Proxmox using an unprivileged container. I skipped the checkbox and reinstalled, which fixed everything. Also, I saw that Docker containers sometimes don’t restart if they already exist with the same name, so I had to remove the old one and rebuild it. If you’re still facing issues, just let me know and I’ll help directly.
C
chayden2k6
08-04-2016, 05:12 AM #5

I resolved it by running it in Proxmox using an unprivileged container. I skipped the checkbox and reinstalled, which fixed everything. Also, I saw that Docker containers sometimes don’t restart if they already exist with the same name, so I had to remove the old one and rebuild it. If you’re still facing issues, just let me know and I’ll help directly.