Skip to content
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

App restart loop in balenaOS 2.32.0+rev2 when overlapping expose / ports instructions are used #970

Closed
pdcastro opened this issue Apr 26, 2019 · 9 comments

Comments

Projects
None yet
4 participants
@pdcastro
Copy link

commented Apr 26, 2019

When an EXPOSE instruction is used in a Dockerfile, and an overlapping expose or ports instruction is also used in the docker-compose.yml file, the supervisor will restart the app container in a loop.

The temporary workaround is to remove the overlapping setting from either the Dockerfile or the docker-compose.yml file.

The supervisor fix has already been merged in this pull request, but this issue was created so we can point to it in forums/support until a new balenaOS release including the fix is released to production.

@pdcastro

This comment has been minimized.

Copy link
Author

commented Apr 26, 2019

25 Apr 2019 update: the supervisor version containing the fix is being merged into the OS. It will then go through testing and the release process for individual device types. The process is expected to take a couple of weeks.

@balena-ci

This comment has been minimized.

Copy link
Collaborator

commented Apr 26, 2019

[pdcastro] This issue has attached support thread https://jel.ly.fish/#/support-thread~5f646b4b-0cbc-4907-92cb-60b3cc38019d

@balena-ci

This comment has been minimized.

Copy link
Collaborator

commented May 6, 2019

[shaunmulligan] This issue has attached support thread https://jel.ly.fish/#/support-thread~1c5b132d-bd72-4d40-a1b6-6ba36c31651b

@imrehg

This comment has been minimized.

Copy link
Member

commented May 6, 2019

This was fixed in supervisor v9.14.4 #964
(cc @shaunmulligan )

@balena-io balena-io deleted a comment from balena-ci May 6, 2019

@imrehg

This comment has been minimized.

Copy link
Member

commented May 6, 2019

@shaunmulligan hm, didn't see your comment in Jellyfish yet, just mentioning that this shouldn't really be an open issue anymore, IMHO, it should be a support issue (how to diagfose in situ) and maybe fix in balenaOS to pull in newer supervisor?)

@shaunmulligan

This comment has been minimized.

Copy link
Contributor

commented May 6, 2019

@imrehg yeah i have created a corresponding support issue in JF, which is what I thought I was commenting on :P

@balena-ci

This comment has been minimized.

Copy link
Collaborator

commented May 6, 2019

[shaunmulligan] This issue has attached support thread https://jel.ly.fish/#/support-thread~29ddd6f1-b01b-4bbf-a0a2-3f76b618716b

@balena-ci

This comment has been minimized.

Copy link
Collaborator

commented May 6, 2019

[chrisys] This issue has attached support thread https://jel.ly.fish/#/support-thread~8d898982-84ea-4a95-8a63-6486078df6d0

@pdcastro

This comment has been minimized.

Copy link
Author

commented May 8, 2019

I see in the meta-balena Changelog that balenaOS v2.33.0 includes the fixed supervisor, so it's now a matter of that OS version becoming available in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.