Tag: update

Posted on

Upgrade flaresolverr docker container

Today I noticed CAPTCHA was not getting resolved in Jackett but without obvious reason. I thought that flaresolverr rlease I was using was outdated so I wanted to try to update it to latest one. First I have checked what I have running:

# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED        STATUS        PORTS                    NAMES
f144c092302c   a88ebf3195a5   "/usr/bin/dumb-init …"   4 months ago   Up 10 hours   0.0.0.0:8191->8191/tcp   flaresolverr

Pulled new image:

docker image pull ghcr.io/flaresolverr/flaresolverr:latest

Checked if the images are there:

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED        SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago    574MB
ghcr.io/flaresolverr/flaresolverr   <none>    a88ebf3195a5   4 months ago   569MB

Stop and delete the container:

docker stop f144c092302c
docker rm f144c092302c

Once container has been stopped and deleted. I have started a new instance:

docker run -d   --name=flaresolverr   -p 8191:8191   -e LOG_LEVEL=info   --restart unless-stopped   ghcr.io/flaresolverr/flaresolverr:latest

Check if new container is running:

# docker ps
CONTAINER ID   IMAGE                                      COMMAND                  CREATED         STATUS        PORTS                              NAMES
e8ec7ca07cf3   ghcr.io/flaresolverr/flaresolverr:latest   "/usr/bin/dumb-init …"   3 seconds ago   Up 1 second   0.0.0.0:8191->8191/tcp, 8192/tcp   flaresolverr

Cleanup of the unused image:

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED        SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago    574MB
ghcr.io/flaresolverr/flaresolverr   <none>    a88ebf3195a5   4 months ago   569MB

# docker image rm a88ebf3195a5

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED       SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago   574MB
Posted on

Fix failed to fetch Google Chrome packages under Debian

Google decided to drop 32bit support for Chrome lately my Debian Jessie is giving me following errors when doing apt-get update

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

To fix the issue you need to edit following file: /etc/apt/sources.list.d/google-chrome.list and change the line:

deb http://dl.google.com/linux/chrome/deb/ stable main

to

deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

Save your file and do normal apt-get update.

It seems that the change in google-chrome.list gets overwritten somehow, so I recommend you to set read only permissions on the file with:

chmod 444 /etc/apt/sources.list.d/google-chrome.list

Remember just next time if you need to modify this file to add write permissions back.