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

sudo: apt update: comando não encontrado #47

Closed
aureliojargas opened this issue May 28, 2018 · 2 comments
Closed

sudo: apt update: comando não encontrado #47

aureliojargas opened this issue May 28, 2018 · 2 comments

Comments

@aureliojargas
Copy link
Contributor

Pra mim deu esse erro ao tentar rodar agora.

$ docker-compose run --name wscef wscef
WARNING: The HOSTNAME variable is not set. Defaulting to a blank string.
Creating network "wscefdocker_default" with the default driver
Gtk-Message: 00:08:08.521: Failed to load module "canberra-gtk-module"
Gtk-Message: 00:08:08.523: Failed to load module "canberra-gtk-module"
Success: created profile 'default' at '/home/ff/.mozilla/firefox/7ewtf7lo.default/prefs.js'
sudo: apt update: comando não encontrado
/home/ff/startup.sh: linha 28: /usr/local/bin/warsaw/core: Arquivo ou diretório inexistente
$

O problema eram as aspas no comando sudo, dentro do startup.sh. Troquei todos os

sudo "comando argumentos"

por

sudo comando argumentos

e daí ele rodou o contêiner.

@farribeiro
Copy link
Owner

farribeiro commented May 28, 2018

Eu fiz este erro banal? Apliquei tal PR #36 e conferi mil vezes! Me auxilie onde ocorreu o erro de interpretação

@aureliojargas
Copy link
Contributor Author

Foi o su -c anterior que te cegou, pois ele precisava das aspas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants