-
Notifications
You must be signed in to change notification settings - Fork 5
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
All branches: Bug with "space tab" in start-squid.sh #3
Comments
Thanks for reporting. Looks like the start script is outdated. I have to copy newer versions of |
I have to correct myself. The script isn't outdated. I just somehow screwed up the "space tab" used in both functions. |
Should be fixed with aee7117 |
last image downloaded. the result when new container created
|
Sorry, I think now it should work. Fix is 789a5d3 Additionally: |
I downloaded bullseye image. now it can build the cache directories here the cache storage scheme set to
|
Aaaaand another bugfix -.- |
the last build of bullseye image now success with
|
my squid.conf
my docker-compose.yml
1- host has user "squid" with UID=1000 & GID=1000
2- host volume directories owner and group set to "squid:squid" with UID=1000 & GID=1000
3- docker-compose up command executed under "squid" user with sudo privileges
sudo docker-compose up
the result
I even tried to run squid container with changed entrypoint to /bin/bash then run
./start-squid.sh
with the same resultI think there is problem with the
start-squid.sh
when trying to create spool dirs because when I disable caching insquid.conf
squid container run without problem and squid logsaccess.log && cache.log
copied to host volume directory./../squid_log
update:
I started the container with these lines commented in
squid.conf
to be able to access the conatiner bashthen after the container started I uncommented the lines in
squid.conf
on host volume directory./config/squid.conf
to enable the cache again then what I did1- the spool directories created and copied to host volume directory
./../squid_cache
2- the owner of volume host directories is
squid:squid
3- the owner of container directories
proxy:proxy
which means
start-squid.sh
failed to create spool directories for some reasonI stoped squid container then
sudo docker-compose up
the result
Originally posted by @srcKod in #2 (comment)
The text was updated successfully, but these errors were encountered: