mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #3336] [bug]: docker aio install error #1111
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gintering1000 on GitHub (Sep 10, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3336
Is there an existing issue for this?
Current behavior
docker pull hoppscotch/hoppscotch-community
docker run -w "$(pwd)/docker" -p 3000:3000 -p 3100:3100 -p 3170:3170 --env-file .env hoppscotch/hoppscotch
Steps to reproduce
docker pull hoppscotch/hoppscotch-community
docker run -w "$(pwd)/docker" -p 3000:3000 -p 3100:3100 -p 3170:3170 --env-file .env hoppscotch/hoppscotch
Environment
Release
Version
Self-hosted
@LoveHeiZhu commented on GitHub (Sep 11, 2023):
I'm having the same problem, is there a solution?
@balub commented on GitHub (Sep 21, 2023):
@gintering1000 can you run the docker container without explicitly setting the working directory.
@Evsio0n commented on GitHub (Sep 22, 2023):
Same issue here.
Attached with my docker-compose.yaml:
Here is attached with my
stack.yamlfor reference:From container
hoppscotch-frontendthe
hoppscotch-frontendhere has quite same issue here withhoppscotch-admin@Evsio0n commented on GitHub (Sep 22, 2023):
Although It's not "issue with AIO" ,
I am following the offical instructions to deploy.
The port is needed to change in either way ( From 8080 to 3000/3100 || Change Instructions)
Thanks 👍
@felixsanz commented on GitHub (Sep 28, 2023):
AIO container is fine. the problem are inside frontend and admin containers