On 01/07/2021 12:26, Pro Turm wrote:
> And also, looks like he's mapping host /tmp to the container.
>
> Why?
>
> This seems to be the reason. I mapped the host /tmp to the dockers /tmp
> to preserve core damps when the docker container stops or is deleted. It
> seems /tmp is loved by
>
> And also, looks like he's mapping host /tmp to the container.
>
> Why?
This seems to be the reason. I mapped the host /tmp to the dockers /tmp to
preserve core damps when the docker container stops or is deleted. It seems
/tmp is loved by everyone (not only firebird) who does important
https://docs.github.com/en/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository
Here is how is setup for flamerobin
https://github.com/mariuz/flamerobin/blob/master/.github/workflows/codeql-analysis.yml
via
On 01/07/2021 10:43, Alex Peshkoff via Firebird-devel wrote:
> On 7/1/21 4:27 PM, Pro Turm wrote:
>>
>> If you use UID/GID in docker with same number as firebird group in
>> host,
>> probably you will not have problem.
>>
>>
>> No, I dont set/use anything explicitly in the docker
On 7/1/21 4:27 PM, Pro Turm wrote:
If you use UID/GID in docker with same number as firebird group in
host,
probably you will not have problem.
No, I dont set/use anything explicitly in the docker regarding UID/GID.
If docker is using install script for linux distro, different
>
> If you use UID/GID in docker with same number as firebird group in host,
> probably you will not have problem.
>
No, I dont set/use anything explicitly in the docker regarding UID/GID.
Am Do., 1. Juli 2021 um 15:08 Uhr schrieb Adriano dos Santos Fernandes <
adrian...@gmail.com>:
> On
On 01/07/2021 09:59, Pro Turm wrote:
> Could the cause for the problem be the following constellation:
> host <-> docker : both use the same FB ?
> I suspect that after quitting the docker, it might set the tmp/firebird
> in the above state.
> What mechanism should FB use, to prevent the above
Could the cause for the problem be the following constellation:
host <-> docker : both use the same FB ?
I suspect that after quitting the docker, it might set the tmp/firebird in
the above state.
What mechanism should FB use, to prevent the above situation ?
Am Do., 1. Juli 2021 um 14:48 Uhr
I have the same situation again. How can I find out, whats causes, i.e.
sets the tmp/firebird in this situation ?
*$ sudo ls -laR /tmp/firebird/tmp/firebird:total 44*
*drwxrwx--- 2 84 84 4096 Jun 30 21:56 .drwxrwxrwt 33 root
root 36864 Jul 1 14:44 ..-rw-rw 1 firebird
