-
Notifications
You must be signed in to change notification settings - Fork 424
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
apps executed inside singularity container doesn't use the same timezone as the host #682
Comments
It seems if I bind the file |
Hi @gmkurtzer This doesn't solve the problem for me.
I did the tests with the latest release |
Hi @pescobar What is the output of:
Return on your host system? |
|
@pescobar I am just curious, are you running the same distribution within the container as on the host? If not, what happens if you do? Is it the same? Thanks! |
Yes. I am running centos 7.3 in both the host and the container. Does this makes any difference? |
It really shouldn't but I thought maybe if the timezone files were of different formats that might explain it... But alas, nope. I'm confused and I can't seem to replicate. |
Timezone? Time? My computer thinks it's 3 hours in the future in one browser but not the other, and I'm ok with this. ;) Non productive comment, yes, but couldn't help myself 😉 |
Haha. You know, if the earth were flat we wouldn't have these problems! Oh wait, maybe we would (http://theflatearthsociety.org/home/).... But I too digress. |
I was testing this same issue a few days ago after posting about it on slack and at that time 2.9.99 didn't have this problem. I just re-checked with the newly released singularity-2.3.0 and the 2.2 problem is still absent. |
@pescobar does the bug persist on your host? |
I tried setting environment
|
This looks to be fixed to me. I could not reproduce the problem using various attempts. Please comment here if you still have problems @pescobar . Thanks! |
while testing singularity I have noticed that a tool executed inside a container is not using the same timezone as the host.
This is the date in the host machine where singularity is executed
And these are the generated logs from the tool executed inside the container:
It seems inside the container is using UTC instead of the host timezone. Is there any solution so the container uses the host's timezone?
The text was updated successfully, but these errors were encountered: