-
Notifications
You must be signed in to change notification settings - Fork 6
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
Squid Cache: Terminated abnormally #2
Comments
Can you please check permission of those directries on your host?
They need to be writeable for a user with UID 13
Also looks like some kind of permission issue. But I'm not sure why. |
my device doesn't have a user with UID 13. |
removed previous squid container and tried again
|
Hmm...Well there is definitely something wrong with permissions on your client. I've tested the arm32v7 image yesterday on my Raspberry and it was working fine. As I'm not able to look into your client to investigate myself, I'm afraid you have to find out yourself why this happens. Some suggestions which could help. ===== Please don't use any user id which could already exist inside the container. User id 0 is definitely already existing inside the container, because it is always the root user. You need to specify some user id which the container can use for a user named squid. Outside your container the user with id e.g. 13 doesn't need to be named squid. It can be any other user. The container dosen't care what happens outside as long as the permissions for the mounted directories/volumes outside are correctly set to be accessible/writeable by e.g. user id 13. ===== You can try to change the entrypoint of the image to
===== Finally there is also an option for |
my squid.conf
my docker-compose.yml
1- host has user "squid" with UID=1000 & GID=1000
the result
I even tried to run squid container with changed entrypoint to /bin/bash then run update:I started the container with these lines commented in
then after the container started I uncommented the lines in
1- the spool directories created and copied to host volume directory which means I stoped squid container then
the result
|
Closing because no reaction from initial poster within 1 month. |
This was just a test. I gave up on docker-squid-proxy because my Linux knowledge is limited. |
Crated container using the command below:
Error log:
The text was updated successfully, but these errors were encountered: